I've just updated Visual Studio 2019 to 16.3.6 which includes the ASP.Net Core 3 SDK.
I create a new project from the ASP.NET Core Web Application project template. The previous version would let me pick the ASP.Net Core version (2,2.1,2.2). Now it does not, and defaults to creating the project using ASP.Net Core 2.2, not 3. Do I always need to manual upgrade every project I create or is there somewhat to bring back the version dropdown or set visual studio to default to Core 3?
I've got Core 3.0 SDK installed:
Then I choose ASP.NET Core Web Application
There are no other core related web projects to chose. Click Next
Then I configure the project There are no options for version, or authentication. I used to see those options prior to the upgrade.
The option is still there. I think you need to install .Net core 3 SDK.
Related
At work, we have an Old application developed with the following technologies:
Visual Studio 2010 Ultimate
.NET Framework 4
C# 4.0
ASP.NET WebForms
With our application we are Highly concerned with issues like:
-security,
-links,
-and users sessions.
We have some new software requirements features which in turn means that we have to add to the existing application.
We would like to use newer Microsoft .NET technologies for the new features.
However, we are concerned about compatibility problems. We have Visual Studio 2019, and we would like to develop the new features using Visual Studio 2019.
But, how far can we go before we have compatibility problems, and face other kinds of limitations?
Is it possible to successfully bridge the Old application with newer technologies like:
-.NET Core Web API
-.NET Core MVC
-.NET Core Razor Pages?
Again, we can Not compromise on the following:
-security
-links
-and users sessions
Yes, you can use both .net framework application and .net core application inside single hosted application. Same thing i have done in one of my project. old project was in .net framework 4.5 and we wanted to build new features in .net core with web api.
We did and integrate both application inside a single application which is hosted on IIS server.
In term of security and sessions , .net core provide more control over these things.
Let me know if you need more help of info.
I am working in Visual Studio 2019, and .net Core 2.1.1.
I am currently working on trying to get Identity Server 4's WsFederation integrated. In the latest instructions I could find, he mentions adding System.IdentityModel to the app through the project.json. Project.json seems to be deprecated now in .net core projects, and I am having a hell of a time figuring out how to add a freaking .net assembly to my project. Do I really need to just copy the file into the project and reference, cause that just seems wrong.
Instructions I am using:
https://www.scottbrady91.com/Identity-Server/IdentityServer-4-SharePoint-Integration-using-WS-Federation
Seems to all come back to the project type. I had created the project with AspnetCore and so I couldn't reference any .net framework assemblies, because you can't go back once you have made that choice. However, if you create the project specifically under the .net framework, you can move forward into the core frameworks, and hosting libraries of core. Which then allowed me to pull in the System.IdentityModel assemblies I needed to continue forward.
I upgraded my Visual Studio 2017 to the latest version i.e. 15.3. I then upgraded the VS Extension for Azure Functions and WebJobs.
When I create a new Azure Function project targeting .NET Core 2.0, it still targets .NET Framework. See below...
This is the project file:
P.S. To be fair, the dialog says .NET Framework 2.0 NOT .NET Core 2.0. So I guess MS means literally targeting .NET Framework 2.0!!!
Update 12/21/17 See newer post here: Develop Azure Functions on any platform
Previous answer
The behavior can be a bit confusing; I've now clarified the blog post: Azure Functions Tools released for Visual Studio 2017 Update 3.
The project type is .NET Standard, but we don't currently support the .NET Standard 2.0 facades in the Azure Functions runtime. Now that .NET Standard 2.0 is RTM, we will make this update in a future release. Once this happens, you won't have to make any project changes other than changing the target framework.
Currently, Azure Functions runs only on full framework, so there is no benefit to targeting netstandard2.0. However, we are porting the runtime to .NET Core, at which point there is a difference. Once that work is complete, the New Project dialog will target netstandard2.0 by default.
I have a visual studio install setup project in which I want to specify that pre-requisite is .Net 2.0
When I click properties-> pre-requisite
it shows only .Net framework 3.5 / client profile and .Net framework 4.0/client profile and other components but not .Net 2.0
The second part is will the installer fail if pre-reqs are not met or install them automatically ?
Thanks,
If you look in the properties for the solution you can select which version of the .NET framework you use. Note this is for the non Express versions only.
http://msdn.microsoft.com/en-us/library/bb398202.aspx
Furthermore Microsoft keeps itself in business by only making VS backwards but not forwards compatible with future .NEzt versions.
To create an installer you needmtomcreatemamDeployment project and specify the dependendcies.
http://support.microsoft.com/kb/324733
I'm having trouble creating a sharepoint project with .net 4.0.
Using Visual Studio 2010, when I attempt to create a new "Empty SharePoint Project", I select ".NET Framework 4" under the .net version dropdown list (actually it's the default selection), and then i click ok. When I look at the "Target framework" property in my package properties, it says ".NET Framework 3.5" and does not list any other versions.
I have assured that .net 4.0 is installed, and I even have another Class Library project under the same solution with version 4.0. I also tried it on a different machine, and the same thing happened. What is going on?
screenshots:
creating a new sharepoint project
newly created sharepoint project properties
other class library project in the same solution successfully using version 4
SharePoint 2010 is built to use v2.0 of the .NET CLR (which is used by .NET Framework 2, 3 and 3.5). .NET 4 uses a different CLR and thus is incompatible with SharePoint insofar as developing solutions to run inside SharePoint.
You can build .NET 4.0 applications that call SharePoint's web services, use the client object model, or even run under a virtual directory under SharePoint. But you're stuck using 3.5 for an actual solution.