Otis wrote:

I use different queries in some areas for sqlserver 2005, because of the fact that you can have a schema without a user in sqlserver 2005.

mmm. I'm not convinced that the differences between these two queries are responsible for the difference I am seeing in speed. The execution plan for the 2005 query shows nothing but Index Seeks and these table hardly contain large row counts...

So far EVERYTHING in 2005 be it visual studio or sql server seems to be really slow...

davisg wrote:

I think I started to run away with myself and decided to install some more Microsoft software, namely SQL 2005 with Business Intelligence (C00l) and Office Tools for VS2005... Well somewhere down the line I have managed to break my copy of VS2005; not so much completely broken but all the menu options to create/open websites has completely disappeared from the IDE

Ok, apparently it was my fault... (or should I say the software install is not intelligent enough; yeah I'll go with that )

The Office Tools for VS2005 has a IDE similar to VS2005 and I managed to overwrite my VS2005 IDE somehow... Microsoft suggest that I install it to a particular directory.... Anyway I completely uninstalled VS2005 and re-installed and everything is now good.

Is it just me or has VS.NET RTM stopped monitoring the project files!!! After I generate, I am no longer being prompted to Reload the project and any files that are open in the IDE are not updated to their new versions until you close and reopen them...

Marcus wrote:

Is it just me or has VS.NET RTM stopped monitoring the project files!!! After I generate, I am no longer being prompted to Reload the project and any files that are open in the IDE are not updated to their new versions until you close and reopen them...

Hmm... You're sure you generated in the right folder?

Otis wrote:

Marcus wrote:

Is it just me or has VS.NET RTM stopped monitoring the project files!!! After I generate, I am no longer being prompted to Reload the project and any files that are open in the IDE are not updated to their new versions until you close and reopen them...

Hmm... You're sure you generated in the right folder?

Yes... The VS.NET 2005 IDE doesn't seem to pick up changed files anymore. If I then Build the project tried to reload then... which is too late and you get a messed up build. Build again and its ok.

This problem gets worse when you add TFS source control. You pull some latest source files and if any updated latest .cs files are open in the IDE, they do not get updated for the build (even thought they are updated on the file system).

Lots wrong with this release...

Marcus wrote:

Otis wrote:

Marcus wrote:

Is it just me or has VS.NET RTM stopped monitoring the project files!!! After I generate, I am no longer being prompted to Reload the project and any files that are open in the IDE are not updated to their new versions until you close and reopen them...

Hmm... You're sure you generated in the right folder?

Yes... The VS.NET 2005 IDE doesn't seem to pick up changed files anymore. If I then Build the project tried to reload then... which is too late and you get a messed up build. Build again and its ok.

This problem gets worse when you add TFS source control. You pull some latest source files and if any updated latest .cs files are open in the IDE, they do not get updated for the build (even thought they are updated on the file system).

Lots wrong with this release...

Please file a bugreport in ladybug http://msdn.microsoft.com/productfeedback . They're now working on patches and a service pack, and they're apparently committed to get fixes out early, which is a good sign, so if you report the issue, they will fix it and a patch will be made available.

You use the beta3 of tfs server?

Otis wrote:

Please file a bugreport in ladybug http://msdn.microsoft.com/productfeedback . They're now working on patches and a service pack, and they're apparently committed to get fixes out early, which is a good sign, so if you report the issue, they will fix it and a patch will be made available.

You use the beta3 of tfs server?

Beta 3 Refresh... Yes I intend to fill out a bug report. Thanks.

[edit] they dont even have the RTM listed under the product versions yet...

[edit 2] Ladybug entry

I've validated it for you, so more people will look at it

Marcus wrote:

Yes... The VS.NET 2005 IDE doesn't seem to pick up changed files anymore. If I then Build the project tried to reload then... which is too late and you get a messed up build. Build again and its ok.

This problem gets worse when you add TFS source control. You pull some latest source files and if any updated latest .cs files are open in the IDE, they do not get updated for the build (even thought they are updated on the file system).

Lots wrong with this release...

One thing that catches me sometimes.. If you use TFS for source control and your LLBLGen projects aren't checked out for editing, the code generation suceeds, but the files won't be updated in VS2005.

I'm still too scared to upgrade to the RTM as it took me long enough to figure out how to work around the issues in the last beta. Does anybody know the best way to uninstall VS2005 b2 and TFS (pre beta3 refresh) for a successful reinstall of the RTM and beta3 refresh versions?

alexdresko wrote:

Does anybody know the best way to uninstall VS2005 b2 and TFS (pre beta3 refresh) for a successful reinstall of the RTM and beta3 refresh versions?

Uninstalling previous betas to prepare for VS 2005 and .NET Framework 2.0 RTM : http://blogs.msdn.com/astebner/archive/2005/10/27/485987.aspx Pre-RTM Uninstall Instructions : http://lab.msdn.microsoft.com/vs2005/uninstall/preRTMuninstall/default.aspx

Migration to the NEW Beta 3 Refresh http://blogs.msdn.com/jeffbe/archive/2005/10/14/481002.aspx http://lab.msdn.microsoft.com/teamsystem/b3rmigrate.aspx

Well at least you all managed to get the %$^&&^** thing to work!!!

It just won't work for me. "Error loading package XXXX"

All because I installed the beta's, and didn't uninstall them in the "right" order..... Ok fair enough there were uninstall instructions knocking about, but they were'nt exactly well publisised, and I didn't do anything radical.

Anyway, if anyone else is pulling hair out and perforing approx 2 installs and 2 uninstalls daily, then this guys a great help: http://blogs.msdn.com/astebner/articles/492809.aspx - still haven't got mine to work yet, but I'm determined NOT to re-install windows!!!

Wish me luck

MattWoberts wrote:

Wish me luck

Hvae you tried the "Hammer" from http://blogs.msdn.com/astebner/archive/2005/10/27/485987.aspx

Marcus wrote:

MattWoberts wrote:

Wish me luck

Hvae you tried the "Hammer" from http://blogs.msdn.com/astebner/archive/2005/10/27/485987.aspx

I started last Friday at 3pm on the upgrade and finished Monday at about 2pm. And that was just for my local SQL2005 Dev and VS2005 TSE installations!!! I did manage to upgrade the server's SQL to the RTM, but haven't upgraded the TFS bits.

"The hammer" didn't help me very much as most of my problems were caused by residual SQL2005 beta stuff. The Windows Installer Cleanup Utility helped a LOT, but I still had to go and manually remove SQL related services from the registry.

After about 8 tries, it finally worked.

Yep, I've been trhough all the tools including the "hammer", and although it succesfully uninstalls everything, theres still dodgy assemblies left hanging around in my GAC, which I can't seem to get rid of....

The only tool I can think of at the moment that will sort it out for me is called "fdisk"

you tried gacutil on the command line to get rid of assemblies in the GAC? at last you can always simply use del on the command line to remove the files from the gac file storage. It's a file structure after all

That was my last attempt (10 mins ago). I had a load of stuff in my assembly folder that looked like it was old beta stuff. I tried gacutil to uninstall and it refused because of depencies to this: SCHEME: <OPAQUE> ID: <{7A1ADD0C-17F3-47B8-B033-A06E189C835D}> DESCRIPTION : <.NET Framework Redist Setup>

Annnyway, I then went down the heavy handed route of deleting the files from the assembly folder, and then rd-ing the folders from the command prompt, thinking that may sort it. But, it didn't. What was weird is that after deleting all these files, when I used windows explorer to look in the assembly folder again, they were all still there - or at least it thought they were.

Hmmm, either I missed some, or my setup is seriously unhappy!!

For the record, the TFS upgrade was cake once I got this working http://alexeyonline.com/archive/2005/11/07/168.aspx

Sorted It wasn't dodgy assemblies after all, it was a dodgy registry. Going through and deleting entries related to 2.0, "team suite", and "packages" seemed a bit ruthless but did the trick!