All -

Trying to upgrade to .net 2005 and have a question.

We need to upgrade 2 copies of visual studio 2003 to 2005 and have no

trouble finding those upgrade prices.  We also have 2 copies of Visual Basic.NET

Standard edition that we would like updated to 2005, but cant seem to find an upgrade

for this.  Do upgrades exist or do we need to buy new visual studio 2005 to replace these?

Thanks much,

Kurt

Thanks for the information.

Would VB.NET Express be the 2005 equivilant of Visual Basic.net 2003?

No, Express is more limited. For example, you cannot create Web sites in VB Express. VB.NET 2003 is closer to Visual Studio Standard.

My advise: DO NOT UPGRADE..

Wait for MSoft to produce a working product which is expected sometime in 2008..

Otherwise you are simply flushing money down the drain, as we did..

Must be a Sun troll.  Studio 2005 is great.  Maybe he's thinking Windows (which I usually wait at least 6 months or one SP before dealing with), but Studio is solid.  There are always going to be bugs that need fixing in projects this size. 

Invest in studio because this guy obviously has no idea what he's talking about.

" no idea what he's talking about."

Amazing how you know everything about someone you could not possible hanve any experience about! I dont know you!!

If your experience with vs  has been fine then share it ( I assume you know at least this much)  but keep out of persoaal attacks when you dont have a clue about my experiences, or the 10,000 of others who have had different experiences to yours....

All I did was comment on the information you gave (none).  Why is it a waste?  What were your problems?  Maybe the rest of us could use the information.

I'm sorry if you were serious, but judging by what you wrote, how could I have deduced much else?

The upgrade requirements for each SKU of VisualStudio is listed on the following page:

http://msdn.microsoft.com/vstudio/howtobuy/renewal/

The way I read it, you can upgrade from VB.net 2003 to Visual Studio Standard, but not to Visual Studio Pro.

Dear larko_s

"All I did was comment on the information you gave (none).  "

In fact you commented on something you clearly could have no idea about..

Keep you comments about something you have knowledge about.

Your own experiences are fine, just stick to the facts that you actually know..

Dude_4,

Listen, I apologized in my last post.  I did neglect to look at your join date and # of posts in my reply to your first post which would have probably tempered my comments as trolls don't usually hang around a forum that long.  Also, maybe I should have given you the benefit of the doubt that you were serious, but given the state of forums and the sheer quantity of trolls on them (I post to over 50 professional and non-professional), I have a bad outlook on opinions without facts.

This is why I asked in my last post why you think it was a waste.  I'm willing to admit when I am wrong, but you have yet to even make a case as to why not to invest.

This is my last post on this matter as I realize that it's off topic.  I urge you to at least give us reasons as to why.  Like everyone is told in school at some point:  "because is not an answer."  That is basically all you have provided.

In an effort to restart the ball rolling back in the right direction, I work for a Microsoft Partner that is staying top of all the new products.  I am currently upgrading all of the old .Net 1.1 code to .Net 2.0.  The biggest problem I have come across actually lies within the SharePoint 2007 library and not the inherent .Net Framework. 

Apparently, they overhauled the SharePoint Object Model and many of the old procedures are depricated and the ones that replaced those don't always have the same effect or parameters.  However, we had already assumed we were going to have to retool the projects that have the most problems because of the changes in SharePoint 2007, so it doesn't really matter. 

The other problem I've run into is the best way to create SharePoint Web Parts in VS2005.  How much has it changed from 2003?  We are still researching the "right way" to create them as most of the documentation revolves around ASP.NET Web Parts and not SharePoint.

Dear larko_s,

"In an effort to restart the ball rolling back in the right direction, I work for a Microsoft Partner that is staying top of all the new products.  I am currently upgrading all of the old .Net 1.1 code to .Net 2.0. "

Background we have had a couple of attempts since last november at moving a 1.1 web project ~ 350,000 line and 10,000 files accross to vs 2005.

The last attempt was with the "final" relase of WAP, which actually did a quite decent job as compared to be fore WAP.

Anyway, the problem was that the vs 2005 VB.net compiler is barely a compiler, and the changes which I suspect have to do with the "back ground VB compile" simple crash with any real projects..

In fact the the compiler misses lots of compile time errors and you end up having to catch them at runtime!!

Vs 2005 designer is broken in many ways, the best example is asp:panel which is unworkable, syyle attributes cause the desiger to baff and for contained controls to become useless..

Now all these things worked fine in 2003, so have been introduced in vs 2005.

Also even basic problems identified and patched in 2003 weree not rolled into vs 2005!!

With this any many many other reasons, inlcuding the breaking Visual Studio etc, lock up crashes which MSoft have known about since nov last year and have NO plans at fxing..

Hence  I make the recommndation that people should NOT use vs 2005 for any real development. It seems to work fine for toy applications..

"The biggest problem I have come across actually lies within the SharePoint 2007 library and not the inherent .Net Framework."

Dont use sharepoint, so have no experience and hence cannot comment..

"Apparently, they overhauled the SharePoint Object Model and many of the old procedures are depricated and the ones that replaced those don't always have the same effect or parameters.  "

As above for sharepoint, but there are "breaking" changes i.e the new funtions which repalce deprecated funtions create runtime breaks!!  For a project of our size this si a night are.

"However, we had already assumed we were going to have to retool the projects that have the most problems because of the changes in SharePoint 2007, so it doesn't really matter.  "

My requireemnst is that vs 2005 is at least as good as vs 2003 and performs basic compiler funtions without locking up and craching..

Ans that compiler problems are caught before runtime..

Not that much to ask surely?

We are used to working around the numious MSoft issue in all their products, ( we did the original development work with vs 2002 final Beta product, so are used to the normal stuff; vs 2002 is way superior to the final vs 2005)... Based on simple A/B tests in all aspects for development vs 2005 is a night mare...

Dear anthony,

I applied 915038, which this one seems to replace ( in fact the file version numbers are identical to this patch)!!..
Hence assuming that MSift even basic CM, the files must have the same content as 915038...

Getting Hotfixes from MS here is a real pain, only slightly less painful than going to the dentist..

Patch 915038 did very little ( it did seem to make the tempfil probelm go away, but still crokes daily), and it is not obvious from the description of 917452 that it addresses any "crash or lockup problems" but perhaps this is MSoft marketing..

What did you find that it fixed?

Thanks..

The problems that it fixed for me:

1.  Painfully slow performance (even just while editing) in Visual Studio when using solutions with multiple (about 10) projects.

2.  Frequent pop-up messages indicating a vbc compiler error/crash, both when I had initiated a compile myself, and randomly while I was editing code.

3.  Errors/warnings staying in the error list even after I've fixed them.

Note, I also did the registry change suggested in the linked article in my previous post.

Dear anthony,

thanks for the Info..

Eventually got the patch from Msoft..

Has been over 4 hours so far, without a crash..., this is the best I have had for the last eight months of using vs 2005..

So hear is hoping..

Thanks again for your help..

Update:

Well hotfix #917452 is the best attempt from MSoft to date, has been almost  week  and only one crash.. So while not fully fixed this is a lot better than hourly crashes and almost usable..

MSoft how about a full/proper fix?
After all it has been almost 10 months that you have known about this breaking problem...

If only I could get my customers to wait for 10 months for a fix...