Please format all IDE warnings and message like the C++ compiler does, i.e. like this:
"FullPath(LineNumber): error|warning IDExxxx: Message string."

e.g.:
C:\Foo\Bar\Mine.sln(1): error IDE4711: The selected file is a solution file, but was created by a newer version of this application and cannot be opened.

Reason: We use a separate PC and scripts to build our entire code base every night. The - very long - build log is parsed and summarized into an HTML file that highlights all warnings and errors.

Yesterday, the following error message appeared in the log file:
"The selected file is a solution file, but was created by a newer version of this application and cannot be opened.
The operation could not be completed. Unspecified error" and MSBuild returned error code 1

It is quite inconvenient to have to extend the parser again and again over time to recognize the errors by matching long literal strings and of course it degrades its performance more and more.

I don't know how to write this suggestions clearer than the current title. I'll try to explain the background of this suggestions
This is the current situations in VS 2012:
1. F# has included as one of first class language since VS 2010
2. F# user base has grown larger than before, thanks to #1, Microsoft! But unfortunately? (read next)
3. Can't create ASP.NET project template using F# other than C# or VB.
4. Can't create WPF (hence Silverlight) project visually using F# (again, other than using C# or VB)
5. Can't create visual Windows Store app using F#, just like #4.
6. Other IDE such as Eclipse has provided great support and also open architecture using open plugin when dealing with Visual Designer on IDE. Therefore any language running on Eclipse can directly add visual designer support on Eclipse, not just Java and C++. It's also easier to create another visual design support for Eclipse for other programming language.
7. Xamarin has provide us F# support to create ASP.NET project and it has proven that F# is not just for numerical analysis and data centric (e.g. type provider) anymore. This will make VS 2012 less appealing to code F# on ASP.NET directly.
8. If there is other language runs on Visual Studio included as part of VS project templates, there's a large possibility it won't have visual design support other than C# or VB. Even C++ in Visual Studio can't be used to create ASP.NET and WPF projects, for example.

Based on those situations, I propose:
1. Make VIsual Studio's visual designers to be extensible and open enough (it doesn't have to be open source) to be available for other programming language to use. I know this will require large rewrite of current VS visual designer, but this closed and exclusive architecture (closed that it's only available on C# and VB) will provide less productivity when using other languages.
2. In accordance to #1 above, there should be open architecture (can be in form of open API) to simply add visual designer if there;s only small languages at initial releases for the next release of Visual Studio.

A sample use case of # 2 is: if there's VS 2015, the Visual designer support may only be available for C# and VB but the Visual designer can be available to be customized and then further repackaged as complete custom project template with visual designer supports for other language such as F# and can be other languages be another G# or Z# (or whatever) as well as long as it runs on top of .NET CLR.

The term visual designer I mentioned here includes current visual designers we have in VS 2012: ASP.NET Webform, ASP.NET MVC, WPF, Silverlight, Windows Phone, Windows Store.

Using XML Comments to store Exceptions information that can be thrown is an excellent way to see what exceptions that can/should be trapped when using a given method. But there is a disconnect with how powerful and effective this could be.

1 <Exception>Comments in exception xml aren't displayed in intellisense</Exception>

2 When writting a catch statement, intellisense could/should pull possible exceptions from the XML Exception Comments for the methods used in the try block.

3 a small tool or wizard should check through all the exceptions thrown by a method, and all the exceptions not caught for methods it calls and automatically fill in the XML Exception Comments

If exception handling like this were to be applied, we could start doing a heck of a lot better producing code that didn't have code errors, and spend more time building code to have less business logic errors.

The Code Definition Window is no longer available in the Express version of Visual Studio 2012; bad idea - if anything, Microsoft should be adding features to the free version of their IDE, not removing them.

This is not the kind of feature that can be thought of as 'professional only' or 'enterprise only'; it's a basic development aid, and it's available in other free IDEs (since before it appeared in VS, actually).

If Microsoft wants to maintain their relevance in the IDE space, and win developers over to the new Store and mobile platforms, crippling the free version is not the way to go.

0

Hi All,

i want some help for Check in & Check Out Process for Classic ASP Pages on Visual Studio 2010.

Currently What i am doing is Goint to.

Files >> Open >> Websites >> Remote Website and Give my Local Server Name there with Port.


Then all the Directory of my Website gets listed out and i Click on Page i want and "Check Out" for edit and once my work is done i want to "Check in" the Page,But i am not getting that option on the List.

So can anyone please let me know,how i will be able get "Check In" option for my page ??.
Or
By What way i will be able to do "Check Out" & "Check in" both Process from Visual Studio 2010.

So once i check in the page its get opened for other to use it.

any help on this would be highly appreciated..Awaiting for some quick reply on it...