Yeah, I think VS2005 is gonna need a beta3.

<< "Can not Switch" in the ASP.Net designer for Inline Style tags | Home | Another reason to use PHP.Net? >>

Yeah, I think VS2005 is gonna need a beta3.

Still way too many ~~issues~~ problems especially with Web projects. Its because there's no single “project file” for the source of assembly references, so basically each page becomes a class library with references.

I'm voting for another beta, if that beta works great, then slam dunk into RTM and we'll start purchasing VS2005. But I *will not* purchase or use any web edition of VS2005 unless I feel that the ASP.Net web project references nightmare can be tamed.

Unforunately, the decision to “break” ASP.Net for version 2.0 seems counter-intuitive. However, its a mistake I don't think they'll make again now that Microsoft is listening more closely to the developer community. I don't think many of us developers that truly love the product would've signed off on such an anarchistic change to VS's handling of Web Projects.

So what does this mean... WebDev might have to work with VS to build asp.net projects? probably. Will the asp.net runtime have to understand and prefer having a Web Project file? most likely. Will web.config become more important for web projects? definitely.

UPDATE: case in point:
Error 38 Indirect reference is being made to assembly Ensoft.Commerce version 1.1.0.21185, which contains 'Ensoft.QuoteSys.Quote.GetShoppingCart'. This Project references a prior version of Ensoft.Commerce version 1.1.0.21004. To use 'Ensoft.QuoteSys.Quote.GetShoppingCart', you must replace the reference to Ensoft.Commerce with version 1.1.0.21185 or higher. C:\WebSites\quotesys\checkout.aspx.vb 401 47 C:\WebSites\quotesys\

Fantastic. So apparently checkout.aspx.vb references a slightly different version (how?) then whats been built. Project references set to AutoUpdate, and still this. Fantastic. I dont even think an army of coders is gonna be able to fix these types of problems when not having a web project file to be the “master”

UPDATE: another error thats very worrysome to me:

Reference required to assembly 'SomeAssembly, Version=4.0.0.0, Culture=neutral, PublicKeyToken=76e79abb81f9b5ae' containing type ''SomeAssembly.SomeType', but a suitable reference could not be found due to ambiguity between 'c:\windows\microsoft.net\framework\v2.0.50215\temporary asp.net files\quotesys\e4b49b96\_shadow\e4d06815\2831720400\29725468\'SomeAssembly.dll', which is referenced by project '2_App_Code', and 'c:\windows\microsoft.net\framework\v2.0.50215\temporary asp.net files\quotesys\e4b49b96\_shadow\e4d06815\3133680288\29725470\'SomeAssembly.dll', which is referenced by project '7_masterpage.master'. If both assemblies are identical, try replacing these references so both references are from the same location.

Print posted @ Wednesday, July 27, 2005 10:08 AM

Feedback

# re: Yeah, I think VS2005 is gonna need a beta3.

did you find a solution to this?

Error 1 Reference required to assembly 'HexNetwork.NET, Version=1.0.0.1, Culture=neutral, PublicKeyToken=1f77f040270eeeef' containing type 'Hexillion.Net.NetworkDatum', but a suitable reference could not be found due to ambiguity between 'C:\Program Files\Hexillion\HexValidEmail.NET Beta 3\bin\HexNetwork.NET.dll', which is referenced by project 'nsupdate', and 'c:\windows\microsoft.net\framework\v2.0.50215\temporary asp.net files\root\8f6db476\_shadow\8bb5e754\2716607232\29727705\hexnetwork.net.dll', which is referenced by project '1_App_Code'. If both assemblies are identical, try replacing these references so both references are from the same location. C:\www\TheAPI-2.0\nsupdate\nsupdate.vb 19 21 nsupdate

Great - I use search on the OS and there is ONLY 1 version out there ... so what's up? 8/7/2005 10:34 PM | Sam

# re: Yeah, I think VS2005 is gonna need a beta3.

Its a maddening situation that is solved with Project file references, that all the pages would use.

The error seems to only affect the design-mode aspect, and not the actual "Build Web Site" (aspnet_compile) 8/11/2005 9:12 AM | Eric Newton

# re: Yeah, I think VS2005 is gonna need a beta3.

VS2005 Really sucks. I developed a web app and now when i deployed to the client it gives all sorts of errors! what the hell?

When it compiles fine on my system, i expect the compiled version not to have any such reference problems.

VS is still not there... 3/20/2006 9:08 PM | Guru

# re: Yeah, I think VS2005 is gonna need a beta3.

The Indirect reference bug is driving me crazy. It's now down to removing and re-adding the affected reference, individually compiling each assembley that uses it and finally building the web project. Each time it takes a good 30-45 minutes out of my day and leaves me steaming.... 7/17/2006 2:56 AM | Lennie Briscoe

# re: Yeah, I think VS2005 is gonna need a beta3.

Manually incrementing the version number in the indirectly referenced assembly's (ie If C refs B refs A && C refs A, then we're talking A) AssemblyInfo file worked for me:

ie 1.0.* --> 1.2.*. 8/31/2006 1:34 PM | Steamer25