Bertan's Blog : MSBee

Building MSBee on Vista

bertaygu — Mon, 11 Sep 2006 21:21:00 GMT

Last week Joe noticed that if you want to build MSBee in Windows Vista, you have to run Visual Studio or MSBuild process under administrator priveleges. This is due to fact that build process tries to install the MSI package once it is created and as a normal user this operation fails under Windows Vista.

Issues with installing MSBee as a non administrator user

bertaygu — Fri, 16 Jun 2006 21:13:00 GMT

MSBee requires administrative rights to be installed and same thing is true for .Net Framework 1.1 SDK as well. If you are running your Windows under a non adminstrator user, you can use MakeMeAdmin script to install both MSBee and SDK.

However as noted in the MSDN forum by Alan, after installing SDK the first time you start Visual Studio 2005, you must have admin rights as well for it to run correctly since it tries to register type libraries from the SDK. After it is launched with admin rights for once, you can continue using it as a restricted user.

MSBee on Microsoft Downloads

bertaygu — Fri, 16 Jun 2006 21:01:00 GMT

Last week we posted signed binary release of MSBee in to Microsoft Downloads, you can download it from http://www.microsoft.com/downloads/details.aspx?FamilyID=e0d0776f-25c4-444a-a6b9-71d06826f5b4&displaylang=en.

We are providing this release for organizations that require signed binaries for installations. Otherwise, the preferred location for downloads is still the project site at CodePlex since signed binary releases only contains code from Microsoft. If you want to see the source code, contributions from the community or latest updates please visit MSBee project on CodePlex.

MSBee RCRFX1_1 configuration file fix

bertaygu — Fri, 09 Jun 2006 02:32:00 GMT

On May, Jamie pointed out on CodePlex that application config file for RCRFX1_1.exe in MSBee was incorrectly named. It was named as RCRFX1_1.config but the correct naming should have been RCRFX1_1.exe.config for it to be actually processed by .Net framework.

Although we have not heard anybody having problems with the incorrect name, I have fixed the issue by renaming the configuration file, updating RCRFX1_1 executable to check presence of RCRFX1_1.exe.config instead of RCRFX1_1.exe and also updating WiX file generating MSBee installer to include new config file. Fixes are now checked in to Codeplex.