First Look at the New C++ IDE Productivity Features in the Next Version of Visual Studio (Cont’d…) |
- First Look at the New C++ IDE Productivity Features in the Next Version of Visual Studio (Cont’d…)
- Connecting Azure and Windows Phone through OData
- Silverlight Cream for September 05, 2011 -- #1143
- Silverlight Cream for September 05, 2011 -- #1143
- Web Forms Model Binding Part 1: Selecting Data (ASP.NET vNext Series)
- NuGet Package of the Week #10 - New Mobile View Engines for ASP.NET MVC 3, spec-compatible with ASP.NET MVC 4
| First Look at the New C++ IDE Productivity Features in the Next Version of Visual Studio (Cont’d…) Posted: 06 Sep 2011 03:16 PM PDT Hi! I am Amit Mohindra, a Program Manager on the Visual C++ team. Earlier in the month my colleague Sumit Kumar had talked about some of the exciting IDE features in the next version of Visual Studio. Today I will just add to that list a few more features that we have done in the next version of the IDE to help you be more productive.
Project Compatibility = No Upgrade (Yay!)Over the years one of the pain points for our customers has been the upgrade cost associated with a new release of Visual Studio . The cost associated with upgrade from Visual Studio 2008 to Visual Studio 2010 especially for Visual C++ customers was steep because of breaking compiler changes and a totally new project and build system based on MSBuild. In Visual Studio vNext we have eliminated this cost for you by supporting project (asset) compatibility between Visual Studio 2010 and Visual Studio vNext. What this means is that you will be able to open and work (build etc.) in Visual Studio vNext with your Visual Studio 2010 projects without needing to upgrade your project files. The upgrade wizard is gone. The upgrade wizard does not pop-up when you load a Visual Studio 2010 project in Visual Studio vNext. It just loads You might be thinking "wait!!!!" if I have more than 200 native projects I don't want to be changing the platform toolset property for each project. We have solved that problem in Visual Studio vNext by providing a way for you to update your toolset right from the solution file. Right clicking on your solution file brings up a context menu from which you can choose to update the toolset for all your native projects. Don't get scared by the word "Upgrade", this option only updates the toolset property for each of your native projects in the solution to use Visual Studio vNext build tools (v110). Note that we are actively working on improving the usability experience around this feature. Note this feature is just not limited to solutions with just Visual C++ project but is valid for mixed solutions as well which might contain some Visual C++ projects and say some C# projects. In the coming weeks you will hear more about this.
Support for Visual Studio Templates (VSTemplates)Visual Studio 2010 and previous releases for C++ offered a way of creating project templates using an old .vsz/.vsdir format. This format is quite old and does not support the functionality of publishing the templates on the extension gallery for other customer to download and consume. Visual Studio vNext for C++ supports the "vstemplates" format for authoring your custom project and item templates that will allow for any new templates to leverage the infrastructure to publish the templates online on the extension gallery. You could either hand author your custom "vstemplate" files using the schema or if you are working on a project you could use Visual Studio to export it to a template as shown below. Just fill out the details for your template and click finish in the wizard. Now go to File->New->Project in Visual Studio vNext and your template shows up. Once you have a template you can also upload the template to the extension gallery by creating a VSIX. Instructions on how to create a VSIX are listed here. You can learn more on VSTemplates here.
SummaryBoth of the features above have been requested by you over the years and we are bringing these to you in the next release of Visual Studio. Please share your feedback regarding these features and we will strive to make them better. Please note that the descriptions and screenshots are from our early internal builds. These features are still under development and could potentially change or not even be included in our final product.  |
| Connecting Azure and Windows Phone through OData Posted: 05 Sep 2011 07:23 PM PDT Don't miss... Webinar recording: Building LOB apps with Silverlight and WCF Data Services Article series: Producing and Consuming OData in a Silverlight and WP7 app The OData series ebook version (MOBI/EPUB/PDF/Word files and source): All SilverlightShow...( read more )...(read more)  |
| Silverlight Cream for September 05, 2011 -- #1143 Posted: 05 Sep 2011 08:58 PM PDT In this Issue: Michael Washington , Tony Champion , Ollie Riches , Gill Cleeren , Koen Zwikstra ( -2- ), Peter Kuhn , Xianzhong Zhu , Mike Taulty , Pete Brown , Sumit Dutta ( -2- ), Asim Sajjad , Dhananjay Kumar ( -2- ), Above the Fold: Silverlight: ...( read more )...(read more)  |
| Silverlight Cream for September 05, 2011 -- #1143 Posted: 05 Sep 2011 08:58 PM PDT In this Issue: Michael Washington , Tony Champion , Ollie Riches , Gill Cleeren , Koen Zwikstra ( -2- ), Peter Kuhn , Xianzhong Zhu , Mike Taulty , Pete Brown , Sumit Dutta ( -2- ), Asim Sajjad , Dhananjay Kumar ( -2- ), Above the Fold: Silverlight: ...( read more )...(read more)  |
| Web Forms Model Binding Part 1: Selecting Data (ASP.NET vNext Series) Posted: 05 Sep 2011 09:58 PM PDT This is the third in a series of blog posts I'm doing on ASP.NET vNext. The next releases of .NET and Visual Studio include a ton of great new features and capabilities. With ASP.NET vNext you'll see a bunch of really exciting improvements with both Web Forms and MVC – as well as in the core ASP.NET base foundation that both are built upon. Today's post is the first of three posts I'll do over the next week that talk about the new Model Binding support coming to Web Forms. Model Binding is an extension of the existing data-binding system in ASP.NET Web Forms, and provides a code-focused data-access paradigm. It takes advantage of a bunch of model binding concepts we first introduced with ASP.NET MVC – and integrates them nicely...(read more)  |
| Posted: 05 Sep 2011 03:26 PM PDT I did some basic mobile view engine work for ASP.NET MVC for Mix in 2009 and then created what I thought was a better ASP.NET MVC Mobile ViewEngine in 2010 . Unfortunately, the second one (the "better" one) had a caching bug that only showed itself in Release mode. This last month, Jon, John, Peter and I updated NerdDinner to MVC 3 with Razor and a pile of other new features . One of those new features was jQuery Mobile support and that meant we need to fix this bad Mobile View Engine. Additionally, ASP.NET MVC 4 will include actual supported Mobile Views support , so the pressure was on. However, we wanted to make sure any new MVC 3 Mobile View sample was mostly compatible with whatever scheme ASP.NET MVC 4 uses. The original folder...(read more)  |
| You are subscribed to email updates from "microsoft" via Ehsan in Google Reader To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google Inc., 20 West Kinzie, Chicago IL USA 60610 | |
No comments:
Post a Comment