Chris Szurgot's Blog

Darn, that Intellisense bug was biting me too. It pretty much makes the Dec CTP unusable. It did seem snappier than Beta 1 Refresh though.

Have you bugged it on the Product Feedback Center yet?

Can't believe this made it past even the CTP-level QA, though...

Kirk, See my next post. It is usable, just not with default Intellisense.

I'm playing around, trying to isolate the problem, and it seems if you remove the snippets, you can leave all the options on, so it might even be a particular snippet.

Ah cool - i never use the snippets anyway. Looking forward to your findings...

Hi, I work on the C# team, and we would love it if you could log this on MSDN Product Feedback. This is the kind of bug we take seriously...its likely that we have fixed it already but I would like to make sure. I plan to run this down when I go to work next week, but if you could post the bug number on this feedback site, that would be great as a concrete tracking mechanism!

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=8c6eab30-28f1-4996-8376-18978c436e4d

Yeah, I tracked it down, and reported it as soon as I could. I've even isolated that you can delete the Snippets in the snippet manager and it'll go away. <grin>

Kirk,

I was excited too; but then realised the .NET build is older than the November CTP. You will note "Application_Code", instead of "App_Code", etc. Thus....This build is really much older than the november build apart from the Team System stuff (ie they must have not merged their branch in their version control system yet).

Thanks for the bug Chris. I'll take a look at this tomorrow and try to let you know if its fixed!

David,

oh weird, no way... but you sure are right...

just noticed Wally's post about the CLR builds with the different CTPs too:
http://weblogs.asp.net/wallym/archive/2004/12/26/332542.aspx

>>
December CTP of Team Studio running build 41115 (distributed just last week on MSDN).
November CTP of Visual Studio Professional running build 41202.
<<

almost one hundred builds is pretty different...

the Team System stuff was a PITA to install anyway. i'm downloading the Nov CTP DVD now...

if you have it installed already, does it include the Unit Testing functionality? it sounded like the Standard edition wasn't going to come with that.

thx,
Kirk

First thanks for the feedback :)
Then, a quick, not very interesting, note on build numbers. Kirk says they're about 100 builds apart. But that's not how build number work. We don't "count" builds that literally.

Each "lab" (a group of several individual team or goup of labs - there is a tree hierarchy up to what we call MAIN) makes a daily build. So 41115 probably means "based on the daily build in the MAIN lab of November 15th 2004". It's a date :) 41202, December 2nd 2004... It doesn't mean it *is* the build made on that day, because after moving up in the tree or closer to a release if a fork is made in the source control that's the date that counts. Then builds will keep the same main number and patch/fixes will be counted with 41115.123 for example.

Knowing the lab and the date allows us to easily know if a build has a good chance include a fix that was made on a previous date or at a later date. Pretty useful stuff. But yeah, they're about two buisness weeks apart.

So, I guess I'm now confused... The December CTP is based on lab date in November, and the Nov CTP is based on a lab date in December. And it sounds like the Nov CTP (made in Dec) would be better if you want to focus on basic .NET development and VS.NET, (I've some bugs I'd like to test and update, but I've been waiting to see if they are fixed) and the Dec CTP would be better if you want to focus on Team Development and Architect stuff (I'd like to, but I don't have the energy (or team) to add in the additional layers for Team System. NUnit, VSS, etc... is good enough for now)

Any clarification on this?

Interesting, the bug that started all this has already been validatated by someone at Microsoft. People, take some time off. <grin>

Chris, first off, thanks for getting a repro on the bug and posting it to MSDN feedback. I checked it out today and cant repro it on the Nov CTP or recent builds. The first bit scares me. If its not too much trouble could you get a minidump of the bug and attach it to the MSDN lab bug? The way to get a minidump is:
a. Start devenv. Lets call it D1.
b. Start a second copy of devenv (say D2).
c. Attach D2's native debugger to the devenv D1 (in D2 go to Tools->Attach to Process, and in the dialog that comes up select devenv.exe in the available processes portion. Then go to the SELECT button in the attach to process dialog, and choose to only debug with Native code type.
d. Once attached with D2, run the original scenario in D1 and watch the crash happen.
e. Once the crash happens, break, and in D2 goto Debug->Save Dumps As, and save the dump file.
e. Attach this file to the repro.

This minidump will help us figure out what is crashing...

Shaykatc,
The original bug entry has been closed as "It does not reproduce in our most recent build." I rolled "forward" (Back?) to the Nov CTP since it was the newer Framework, and I'm still seeing a variation of the issue in the Nov CTP, but it's damned intermittent. It showed up an hour ago, right before I saw your last comment, now I can't seem to repro it at all.

So do you want me to repro it in Dec CTP (I still have the disc image) or wait till it reappears in the Nov CTP (I'm sure it will, it's been there for the past few weeks, I was waiting for the Dec CTP since I thought that was newer)

Chris - could you email me at my user name + at microsoft.com? I checked the Nov CTP yesterday and didnt see it repro...and for some reason I thought you were seeing it in the Nov CTP. The Dec CTP is older (complex isnt it...?) and its going to take me a little bit longer to find a machine with it on. If you could email me that would be great so that I have your email, and dont have to check this thread always :-)

The December CTP made it out during the Month of December. It is of the VSTS bits and you can read more about it