Ms vnext

Today we released updates for ASP.NET vNext in Visual Studio “14” CTP 4. This release includes the ASP.NET vNext runtime and tooling improvements as outlined below.ASP.NET vNext RuntimeThis CTP includes our alpha4 runtime packages for ASP.NET vNext. You can find details on the specific enhancements added and issues fixed in the published release notes on GitHub.For information on how to get started with ASP.NET vNext using Visual Studio “14” check out the article Getting Started with ASP.NET vNext and Visual Studio “14”.The MVC Music Store and Bug Tracker sample projects have been updated for this release. You can find instructions on how to open, build, run, and publish these sample ASP.NET vNext projects in the documentation in the corresponding GitHub repos.There are a few notable breaking changes in this release from Visual Studio “14” CTP3:Project.json now uses “aspnet50” and “aspnetcore50” as framework values, instead of “net45” and “k10”.Project.json has a new “webroot” element to indicate the static content folder and an “exclude” element for folders to be excluded from compilation.The Startup.cs IBuilder parameter was renamed to IApplicationBuilder.ASP.NET vNext ToolingPerformance improvements to compilation in Visual StudioVS uses the Roslyn engine to compile ASP.NET vNext projects at design time. Therefore the project has already been compiled when you issue a “build” request. In Visual Studio “14” CTP4, VS simply passes the design time compiler output to the build request. This avoids another build and improves performance when you build, run, or debug ASP.NET vNext projects.NuGet Package Manager supportVisual Studio now supports the NuGet Package Manager and console for ASP.NET vNext projects.To use this UI for upgrading current alpha ASP.NET vNext packages, click the Settings button and add package sources from developing sources: for packages built from github.com/aspnet master branches for packages build from github.com/aspnet dev branchesNew layout for ASP.NET vNext solutions and

F5 in an ASP.NET vNext project does not work for the Core CLR framework. Ctrl + F5 works fine. Pressing F5 works fine for core CLR framework on Windows 8.1.4. Three Core CLR package versions were downgraded due to a restructure of the Core CLR packages. If you installed VS “14” CTP4 on a machine that you’ve already used ASP.NET vNext on before, clear out %userprofile%kpmpackages to ensure projects can successfully build and run. They are:System.Text.Encoding from 4.0.20.0 to 4.0.10.0System.IO.FileSystem from 4.0.10.0 to 4.0.0.0System.IO.FileSystem.Primitives from 4.0.10.0 to 4.0.0.0SummaryWe’d love to hear your feedback. For Visual Studio tooling related issues, please submit bugs through Connect, send suggestions on UserVoice and quick thoughts via Send-a-Smile in the Visual Studio IDE. For ASP.NET vNext, please provide feedback in GitHub or the ASP.NET vNext forum. If you ask a question in Stack Overflow, use the asp.net-vnext tag. Thanks for being with us in this exciting time! Author

ProjectsASP.NET vNext solutions created in project template now has a new project layout. While this new layout is not required, it helps with cleanly separating your application source code from other artifacts in your solution. New solutions now contain a src folder for your application projects. A top level global.json file indicates the src folder can be used for looking up project references. This makes it easy to separate test code under a different folder, but still be able to reference application projects from your test projects. For test projects, we recommend to put them under test directory. ASP.NET vNext web project template also puts static contents under the wwwroot folder that is determined by the webroot element of project.json.Global.json file in new solutions for project-to-project referencesIn the previous picture, you can see a global.json file in the same level as the solution file, to make better support for project-to-project references. It contains “sources”: [“src”] element, indicating the “src” folder as the parent folder for looking for project references.By default, project-to-project references lookup will use parent directory, plus the global.json-defined directories. For example, we have the following solution structure and project.json dependency visibility:Solution1global.jsoncontent {“sources”: [“src”] }Solution1srcWebApp1Possible Dependencies: ”ClassLib1” :””Solution1srcClassLib1Possible Dependencies: ”WebApp1” :””Solution1testTestProj1Possible Dependencies: ”WebApp1” :””, ”ClassLib1” :””, ”TestProj2” :””Solution1testTestProj2Possible Dependencies: ”WebApp1” :””, ”ClassLib1” :””, ”TestProj1” :””We only need two simple steps to add an ASP.NET vNext class library reference to the default ASP.NET vNext web application.1. In Solution Explorer, add a new project under the “src” folder. Note, we need to append the “src” folder to the “Add New Project” Location edit box manually at this time. (VS will do this automatically in a future release.)2. Open web project’s project.json file, add “ClassLibrary1”:”” inside the “dependencies” elementDebugging support for ASP.NET vNext unit testsIn VS “14” CTP3, support was added for

By the end of 2020, a couple of interesting things regarding Exchange server are going on. The first one we've know about for a long time, is the end of support for Exchange 2010 in October 2020. After almost 11 years, Exchange 2010 is no longer supported by Microsoft. It continues to work, but don’t expect any technical support, update Rollups or even security hotfixes.Microsoft has been pushing hard on this, but a recent study by security company Rapid7 showed that they still found approx. 140,000 instances of Exchange 2010 OWA published to the Internet. So, still a lot of work to do here.More exciting news from Microsoft, and for a lot of people that thought Exchange 2019 was the last on-premises Exchange version, was the announcement at Ignite 2020 that in the second half of 2021 a new on-premises version of Exchange will be released, current codename Exchange vNext. I still call it Exchange 2022, but the official name will be announced by Microsoft later.Exchange vNext will support Exchange 2013, 2016 and 2019 in the same topology. This is a major difference from earlier versions where Exchange only supported the last and second to last version in coexistence. So now it is possible to upgrade from Exchange 2013 directly to Exchange vNext without installing Exchange 2016 or Exchange 2019 first. Related to this, you can have a load balanced array of Exchange servers with all four versions behind one load balancer. This makes upgrading a lot easier. Of course,