I have just upgraded my .Net frameworks to 2.0 release version, and in the process, I had to uninstall the previous beta version and also some other stuff like the compact framework.
Now, Visual Studio beta2 is not launching anymore. Is this a known issue
With kind regards.
.Net 2.0 release version breaks VS 2005b2?
Hot Topic
- Addressing a Thumb Drive in Software
- How to maintain security on server with socket applications
- Problem Creating Dataset
- Assembly class -- Cannot release its resouces after loadfrom
- Calling a webservice using Soap1.2
- How to Deal with Pop mail
- single transaction between different methods
- WSE signed message throws SecurityTokenUnavailable error
- How to post large contents using HttpWebRequest ?
- Saving csv to Sql Table
.NET Development
- Listbox Selection Event
- ref/out being messed up in my WS, how come?
- Process.Start() of xcopy only works under the debugger?
- Reading CSV files
- C# - OleDb - Access(MDB) : storing and retrieving images
- "invalid handle", sockets, threads and garbage collector
- Enumerating Running Applications in C#
- Invoke SetPassword C# LDAP provider...Whos got the fix??
- Problems with my Visual Studio .NET 2003 IDE
- Working directory problems
.Net 2.0 release version breaks VS 2005b2?
krus
I wouldn't call it an "issue", and I'm surprised you even expected it to work. But yes, VS versions are pretty tightly coupled to a corresponding Framework version.
Justin Y
I must agree with that.
Any official statement from any MS team would be welcome :-)
Specially if there's a way to have my workstation usable without reinstalling the old software.
swfblade
How deep is the project that you have been using beta 2 I was nervious at first when I loaded my beta 2 huge project into... i think either August ctp or the RC and there were quite a few failures.
The datasets fail because of the changes in the system.nullable feature. You can take your current dataset and just delete the tables one by one re-adding them in the same file and that should work. (I wouldn't suggest it on large project because of the fun trouble shooting is) Anyways, the change got me into using it(system.nullable) as I was previously uninterested, now I use it in all of my structures, classes, everywhere. It is very very useful.
The other small things that I noticed is that some of the controls had either black back colors or just errors in the style fonts. I couldn't explain it but I didn't really take the time to care.
I wouldn't say that there were major architectural changes, other than the ide works extremely better. Starting since the august ctp it has been quite a bit more responsive 200%+ less failures.
As far as my project I basically started over.. again. I think i have done it for every release installed. Never disappointed though, through all of the changes its made me realize the great features available.
Brihadish
(hopefully for the performance...)
Plus, if there are as many difference as you're telling me, it's very bad for my current developments and it shows nothing but poor design from the .net team. beta software are not ment to have major architectural changes, and beta APIs shouldn't have major architectural changes neither, otherwise you are building your code on a moving framework. Nothing good can come out of this...
WendellwithSBSatMS
I understand that this is actually not the case, since I had to uninstall the previous beta to install the final (they still have different version numbers right ).
Plus, I don't really understand why and IDE would not work if I install a new version of some libraries (since the IDE is not .Net only, it's only some librarires which have been changed...).
These two simple reasons make me belive that this is any issue, and not a feature...
And VS2005 final is not available in the retail market yet...
Arumugam J
IMHO,
Michael Taylor - 10/31/05
bananas
You can't be serious right Dude, absolutly will it break. If you have ever read the instructions you'll see that for one, if you ever uninstall the .net 2 framework (regardless of the release) it needs to be the very last component removed. If any components are left installed that require the uninstalled framework they will not remove properly afterwards.
There is that vsuninstall tool that can help in that situation. But there were some substantial changes in the beta 2 to the release framework. There is no way for beta 2 software to run off of any other framework. It wont work with any of the ctp frameworks either.
Oh and neither will most of the programs you wrote in beta 2, hah. Well at least without some work. (Datasets specifically)
tom_g
regards,
Alan.
BadMojo
That's only true for different releases (basically different major or minor version number), not different builds of the same release. For example you can have v1.1 and v2.0 installed side by side, but not v2.0.xxxxx and v2.0.yyyyy.
>Plus, I don't really understand why and IDE would not work if I install a new version of some libraries
The .NET framework consists of a lot more than just "some libraries". It's also the CLR, debugging services etc. There has been significant changes between beta 2 and RTM.
> If they are that tightly coupled, they should be released together.
They are released together. VS includes the correct version of the framework and SDK.
smehaffie
One, ClickOnce docs tell you all about how it downloads the most recent version of the .net framework. Yea it feels like *** when you run into that problem but remember, you are beta testing. You are suppost to be telling them bugs and helping with the overall release... which brings me to the next thing.
They can, and did (yesterday) release all of the necessary elements that work together perfectly, hense "Release".
How can someone smart enough to write their own code, test it, and deploy it, even make coments regarding intermingling of beta components. I have tested so many ctp's and over 99% of the time that i had a problem it was because I didn't take the time to go over the included directions properly.
Microsoft is going off with everything that they are doing. Can you imagin even being part of such intergration. Most people can't get the components in their own program to have proper communication with the rest of their classes. At the vslive in orlando it seemed like most of the developers there have been coding in notepad for years and all i heard were complaints. No offence but get your head out of your arse and watch some web casts or format your box and read the install procedure.
tw_16
Laitu
People who make comments about how beta versions shouldn't work with anything that is released are truly short-sighted. Not releasing such tightly interrelated software simultaneously does not make sense. I expressed this same concern some months ago because so many parts of the VS Express packages did not work together. I gave up on it but came back in Sept because MS seemed to have gotten its act together. I was wrong.
MS, don't tell us (developers) that you have an integrated suite of development tools if they don't work. If you can't release all the necessary elements that must work together at the same time they don't release them until you are actually ready to release an integrated package.
Fortunately for microsoft its competitors are too weak to compete. But, MS just is not the company it used to be. In the old days, MS was good to the developer community. Nowadays, they just don't seem to care.
ysucek
That is great news! Can you tell me where I can download or purchase the released version of C# Express The main Express web site still has the beta version that won't install with the released .Net framework.
regards,
Alan.
Dylan McAtee
regards,
Alan.