Wednesday, September 21, 2005 10:55 AMI have both Visual Studio .NET 2003 Pro and Visual Studio 2005 Pro August CTP installed on the same machine. I am doing this with the understanding that when VS 2005 is released as RTM, it will be expected to coexist with older versions of Visual Studio, while people are trying to transition from the old to the new.
I have made a custom project type with the necessary .vsdir and .vsz files. Currently, that custom project only works with VS 2003, I haven't made the registry changes necessary to get it to work with VS 2005, that's fine so far, I just create a project from that template with VS 2003 and then convert it for use in VS 2005.
The .vsdir and .vsz files are read-only on my computer (checked into source control).
Recently I was working with some actual C# projects created using this custom template. I noticed while building that I got a dialog complaining that line endings in a file were not right. I don't remember being told which file had the problem, I just assumed it was one of the source files, and said OK for the IDE to change them.
Well, apparently the file it was complaining about was the .vsz file, because after using VS 2005, I cannot create a new project in VS 2003 using that custom template, I get an error saying that the .vsz file is corrupted. I checked, and the .vsz file has been modified from a Unix-style file with \n for line endings, to a DOS-style file with \r\n line endings. This caused VS 2003 to choke. When I manually changed the line endings back, VS 2003 works fine with the custom template.
I think it is a really bad problem that VS 2005 is needing the .vsz files to have different line endings and therefore conflicting with VS 2003, UNLESS I am mistaken in trying to use a custom template designed with VS 2003 in VS 2005. If that's the case, then fine, but I haven't seen any kind of notice about that in the VS 2005 CTP Readme's, but please let me know if I've overlooked something.
Anybody else seen this? I am planning to install RC1 tomorrow, so I'll post again if I see this continuing to occur with that version.
Friday, October 21, 2005 9:38 PMAre you still seeing this problem?
Monday, October 24, 2005 11:29 AMI have been using VS 2005 RC since it was released, and no, I haven't seen the problem again, so I'm hoping it was fixed, or the original occurrence was caused by a gremlin :)