MSMVPS.COM
The Ultimate Destination for Blogs by Current and Former Microsoft Most Valuable Professionals.

Visual Studio 2008 error notification...when not to make sense

Brian H. Madsen - .Net Powered by Caffeine

Feeds

A colleague of mine who's working on the same project as I am, got an error today in Visual Studio 2008 (when he was building the app) which just made a lot of sense...or..did it.

this_makes_sense

Brilliant!!! "The operation completed successfully" is registered as a build error.

Technorati Tags:

Posted May 29 2008, 12:45 PM by Brian Madsen

Comments

Colin Scott wrote re: Visual Studio 2008 error notification...when not to make sense
on 05-28-2008 22:48

To be fair there are elements of Visual Studio 2005 that do appear like successful operation was considered a bug during development. Even with Service Pack 1 it's still only marginally beta quality. 2008 is on the whole much nicer.

Colin Scott wrote re: Visual Studio 2008 error notification...when not to make sense
on 05-28-2008 23:04

My particular favourite build issues are when Visual Studio has locks on files that prevent the build from succeeding. I probably need to kill a VS instance once or twice a week on average to resolve this. I've tried in the past to add MSBuild copy commands to project files to automatically copy various assemblies into a common output directory but invariably this runs into file locking issues that make it simply not worth the effort. Which is annoying.

Brian Madsen wrote re: Visual Studio 2008 error notification...when not to make sense
on 05-29-2008 18:46

Hey Colin,

yeah - there's a few problems with things like builds..

i've found another nuisance and that's when you work with SharePoint Sequential Workflows and press F5. This deployes the workflow to the library/list that you set up, but if you're running under source control (eg. TFS in this instance) and haven't checked all files out then you'll get an error when you deploy it again. the file is read-only. Why Visual Studio can't figure out that it needs to remove the properties from the file when it deployes it is beyond me. Afterwards you have to locate the .xml files and manually either remove the read-only property or delete the files.

small idiosyncrasies :)



Copyright © is the original authors. Blog site is an independent site not sponsored by Microsoft. The Yoda blog server and the Brianna SQL server would like to thank www.ownwebnow.com and www.exchangedefender.com. They wouldn't be here and broadcasting without the generosity of Vlad Mazek and his companies.

Powered by Community Server (Commercial Edition), by Telligent Systems