MSBee Work Item Rss Feed

COMMENTED ISSUE: Integrate MSBee with .NET 3.5

aikson — Fri, 08 Feb 2008 14:44:55 GMT

Currently building with .NET 3.5 seems to have problems with building .NET 1.1 applications with MSBee.

This issue item is to see if we can integrate MSBee with .NET 3.5.
Comments: ** Comment from web user: aikson **

This realy would be great.
A lots of people had legacy code in .Net1.1 but also want to use new build features .Net 3.5 offers.

COMMENTED ISSUE: MSBeeSetup claims that .NET Framework 1.1 SDK is not installed

rprouse — Thu, 17 Jan 2008 20:44:07 GMT

This is happening to me too. I am running on Vista, I have installed the 1.1 SDK several times. I have also installed the 1.1 redist and 1.1 SP1.

Any ideas? Is SP1 causing the checked registry location to change?

COMMENTED ISSUE: Integrate MSBee with .NET 3.5

iamhere — Tue, 11 Dec 2007 17:06:10 GMT

I also have "FrameworkVersion35Path" error in my project, when trying to build it under .net 3.5 and msbee.

COMMENTED ISSUE: Integrate MSBee with .NET 3.5

ciqkid — Fri, 07 Dec 2007 16:48:36 GMT

One of our products is a plugin for Office XP Excel which only supports .NET 1.1. Our other products are built in 3.5 but the shared codebase is in 1.1.

CREATED ISSUE: Integrate MSBee with .NET 3.5

Jazzynupe — Thu, 01 Nov 2007 05:51:38 GMT

Currently building with .NET 3.5 seems to have problems with building .NET 1.1 applications with MSBee.

This issue item is to see if we can integrate MSBee with .NET 3.5.

COMMENTED FEATURE: Add support for web references

jack78 — Thu, 07 Jun 2007 16:50:03 GMT

If you convert a VS 2003 project with web references to VS 2005, build errors are produced when building with MSBee. This forces a user to manually revert converted files to keep them .NET 1.1 compatible. Trying to provide a way to automatically filter out or undo the changes that are incompatible with .NET 1.1 would improve a user's experience with MSBee. Comments: ** Comment from web user: jack78 **

I agree! Developing for Microsoft CRM 3.0 that supports only .NET 1.1 and all is done using web references - we really need it!

CREATED ISSUE: Straight install gets error MSB1008

BruceHaley — Thu, 03 May 2007 22:46:31 GMT

The Problem: When doing a straight install using all defaults, performing the instruction in MSBee ReadMe.doc at section 4.4.2, the following error is generated: MSBUILD : error MSB1008: Only one project can be specified. The Fix: Update the command in section 4.2.2, adding quotation marks as in: msbuild [project file] /p:TargetFX1_1=true /p:CustomAfterMicrosoftCommonTargets="%ProgramFiles%\MSBuild\MSBee\MSBuildExtras.Fx1_1.CSharp.targets" The attached Word file, MSBee ReadMe.doc, contains this fix. Thank you. --Bruce

COMMENTED FEATURE: Integrate MSBee into the VS 2005 IDE

jahbreeze — Wed, 31 Jan 2007 14:36:49 GMT

See initial comment... Comments: ** Comment from web user: jahbreeze **

This sounds great! MSBee wihtout the GUI enhancement is pretty cumbersome to setup and enjoy.

CREATED ISSUE: GenerateResource - Command-lines longer than 32000 characters

asecbdubas — Wed, 17 Jan 2007 15:10:13 GMT

Hi, I have fallowing porblem... After converting web project and add required imports in csproj file i have fallowing error message durning resources compilation.. C:\Program Files\MSBuild\MSBee\MSBuildExtras.FX1_1.Common.targets : warning MSB6002: The command-line for the "GenerateResource" task is too long. Command-lines longer than 32000 characters are likely to fail. Try reducing the length of the command-line by breaking down the call to "GenerateResource" into multiple calls with fewer parameters per call. Project contains lots of pages and all of them have own resx file so this is why this error ocured. If it is possible the task schoudl check the command line and divide it to two or more comand calls to ommit this problem. Actualy i remove the resx file to check that it will be compile and working so its not a reeal issue right know but it schoudl work wor larga naumber of files and not depend upon file numbers. I wonder how the csc.exe task will bechawe in this situation...i will check it after remuwing resx files form project...and if it will have teh same issue i will let know.

CREATED ISSUE: unit test code compile fails

poobah — Fri, 29 Dec 2006 16:09:23 GMT

Compile fails for unit test code written in VS2005 that uses 1.1 versions of NUnit or MbUnit if using a VS project referanc. steps to repro create test project add nunit/mbunit referance using referances/.NET try and compile using msbee If file is copied to project bin folder and referance changed then it works. I noticed that msbuild is excluding the nunit.framework.dll or mbunit.framework.dll referances when run through MSBee but ok when run normally.

COMMENTED FEATURE: Add support for web references

gholliday — Thu, 28 Sep 2006 01:26:37 GMT

COMMENTED ISSUE: MSBeeSetup claims that .NET Framework 1.1 SDK is not installed

bertanaygun — Fri, 15 Sep 2006 22:46:01 GMT

Well the summary says it all. When double clicking the MSBeeSetup.msi I get an error message saying that Framework SDK 1.1 is not installed. Could it be because I use a non-defalut culture (language pack)? Comments: ** Comment from web user: bertanaygun ** It should not be because of the culture as MSBee checks a registry location to make sure SDK is installed. For MSBee, you must have both .Net 1.1 Framework and .Net 1.1 SDK installed. You can try downloading the SDK and reinstalling from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=9B3A2CA6-3647-4070-9F41-A333C6B9181D&displaylang=en

CREATED ISSUE: MSBeeSetup claims that .NET Framework 1.1 SDK is not installed

jarlen — Fri, 15 Sep 2006 10:55:19 GMT

CREATED FEATURE: TypedDataSet support

popove — Wed, 19 Jul 2006 21:10:22 GMT

This is the VS2005 project for VS CustomTool. This custom tool executes xsd.exe from .Net 1.1 and generates classes which could be compiled using MSBee

CREATED FEATURE: J# support

popove — Wed, 19 Jul 2006 20:40:10 GMT

This targets for J# supporting in MSBee

CLOSED ISSUE: Delimiter used in ResolveComReference causes problems

bertanaygun — Mon, 17 Jul 2006 23:14:40 GMT

When a project has a COM reference and a project reference, ResolveComReference task fails because project reference's metadata contains '|' character which is the delimiter used in ResolveComReference task. Comments: Resolved with changeset 1378.

CREATED ISSUE: Delimiter used in ResolveComReference causes problems

bertanaygun — Sat, 15 Jul 2006 06:10:45 GMT

CREATED ISSUE: Resource-filename handling like VS2003 + workaround

SPeedY — Mon, 03 Jul 2006 13:00:17 GMT

Suppose you have a resource file located in a subdirectory called 'subdir' relative to the project file. If you compile the project with VS2003 it generates an obj file with the convention NameSpace.subdir.ClassName.resources and this is not the same output with MSBuild + MSBee1.0. So if you try to load resources in a way like: ResourceManager resources = new ResourceManager( "NameSpace.subdir.ClassName", Assembly.GetExecutingAssembly() ); the MSBuild + MSBee generated assembly leads to an error. I think the bug / feature is located in the behaviour of VS2003. project constellation: ProjectDir |_ project.csproj subdir |_ ClassName.cs ClassName.resx |_ obj |_ FX1_1 |_ Debug |_ NameSpace.ClassName.resources // MSBUILD + MSBee1.0 |_Debug |_ NameSpace.subdir.ClassName.resources // VS2003 One workaround: #if FX1_1 const string resourceSource = "NameSpace.ClassName"; #else const string resourceSource = "NameSpace.subdir.ClassName"; #endif ResourceManager resources = new ResourceManager( resourceSource, Assembly.GetExecutingAssembly() );

CREATED ISSUE: Use the general AssemblyFolders registry key to find referenced assemblies

alanjmcf — Tue, 13 Jun 2006 19:22:50 GMT

It is recommended that third-party libraries add their on-disk location to a registry key to tell VisualStudio where to look for any referenced assemblies. MSBee 1.0 does not look in the main recommended registry location. The document at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/vstch_multivercomponent.asp lists the various locations that Visual Studio 2003 will search for "components". It says: • If the component is to be registered [...] only for Visual Studio .NET 2003, then register in HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\7.1. [...] • If the component is to be registered [...] for all versions of Visual Studio, it should be registered in HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework. (There are also per-user equivalent!) Two third-party libraries that I am using (one being NUnit) only register themselves in the latter location, correctly per the specification in that document. MSBee currently however only looks in the the former location (...\vs\7.1\af). It should look in the general location too. See our discussion in the forums on this at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=461079&SiteID=1, and a workaround there.

CLOSED ISSUE: 'RCRFX1_1.exe.config' not 'RCRFX1_1.config'

bertanaygun — Mon, 05 Jun 2006 21:25:30 GMT

The app config file for 'RCRFX1_1.exe' should be 'RCRFX1_1.exe.config' not 'RCRFX1_1.config'. Comments: Config is now named correctly, also RCRFX1_1 binary is updated to check for RCRFX1_1.exe.config now.