I have a stable webapp application currently in production env developed using .NET 4.6.2. I tried to update the project to 4.7.2 but I received several error related to some Nuget packages used. So, for the moment, I stopped the upgrade.
My question is very basic: assuming I don't have particular requirements forcing me to upgrade the .NET version, what reasonable advantages would I have in upgrading the .NET framework?
In other words: is it advisable, suggested, a best-practice? In particular, but not only, referred to safety/security and performance of my webapp?
Related
Which thing makes asp.net core a cross-platform?I tried search on google but did'nt see anything regarding to this that what are the things that makes .net core a cross platform.
Microsoft has made a .net core runtime and a SDK that is compatible with Linux and MacOS. If you go to https://dotnet.microsoft.com/download you can download one of these products and start developing/running programs on a non Windows environment. In the past, there was no runtime that allowed you to execute .net program on such an operating system. You can see this on the downloads page: the only OS supported for framework 4.8 is Windows. If you want to start cross platform .net development, just open up a linux VM and install the appropriate runtime as well as visual studio code.
I am trying to install the QuickBooks SDK v13 on a windows 10 computer for development and then again on a Windows 2016 Machine for production use.
I am getting stuck in a loop of trying to install old .Net Frameworks.
I am following these instructions:
https://developer.intuit.com/docs/01_quickbooks_desktop/1_get_started/20_download_and__install_the_sdk
Here are some of the screens I am seeing stepping thru the instructions:
I am posting this on Stackoverflow because this is an installation of an SDK problem.
Is there a way to run the installer with .NET Framework 4.x?
Am I using the wrong version of the installer? It seems very strange that is requires such an old version of .NET Framework.
I can try to figure out why the old .NET Framework versions do not install but before I do that I want to determine if I am off track with something related QuickBooks.
At this time I am not going to try to install old versions of .NET. I am going to confirm that the QB SDK actually needs those versions or find out if there are different SDKs that use current technology.
I just clicked "No" on the "Would you like to install it now?" question and it seemed to install fine.
However, I did get this AFTER the install of the sdk:
This leads to the next question: does Quickbooks SDK use .NET Framework 3.5 or does the installer use 3.5?
At first, I built up a ASP.NET5/MVC6 project with .netcore in VS2015 community, everything was OK. With going deeper and deeper. I have to use session or tempdata, but after I add microsoft.netcore.session package, package restore will fail and all my existing package got NU1002 error said: NU1002 the dependency XXXX in project XXXX does not support framework DNX, version=v4.5.1. Like the picture.
Error on all packages
But if I uninstall the session package, eveything is OK. What's wrong with this ? My sdk version in global.json is 1.0.0-rc1-update1 and I have removed DNX5.0 from project.json. Does anyone could help me?
According to your screenshot you are using DNX framework in your project, which should be the old version ASP.NET 5 project framework. After ASP.NET 5 upgrade to .NET Core, the framework is now called .NETCoreApp. And the SDK version now is 1.0.0-preview2-003121. The error message also means the dependency does not support framework DNX. I have installed the Microsoft.AspNetCore.Session package successful in my Visual Studio 2015 with latest .NET Core SDK version.
So I suggest you download the latest .NET Core SDK installer from below link and then create a new .NET Core application and then move your original project files to the new project and then install the session package.
https://www.microsoft.com/net/download
If your project is create by ASP.NET 5 RC1 project template, please refer to following article to migrate it to ASP.NET Core 1.0.
https://docs.asp.net/en/latest/migration/rc1-to-rtm.html
I have upgraded the server to ASP.MVC 5.
In Control Panel in Installed Programes, I found:
ASP.NET MVC 2
ASP.NET MVC 3
ASP.NET MVC 4
ASP.NET MVC 4 Runtime
It is safe to uninstall all of this older ASP.NET MVC? There is no ASP.NET MVC 5 in list. It is because it was installed via Nuget?
MVC is bin deployable - meaning that you don't have to install it at all if you don't want to. Earlier versions of MVC were easier to run if you had installed them, so this is probably why you have installations.
By default, anything you fetch from nuget is bin deployed (as it isn't installed on your machine, the files are added to your project).
You can safely remove any installed MVC packages - and if you do have projects that depend upon them, you can install MVC in any project using nuget, and specifying a version (back to version 3) - for example:
Install-Package Microsoft.AspNet.Mvc -Version 3.0.50813.1
Install-Package Microsoft.AspNet.Mvc -Version 4.0.40804
Install-Package Microsoft.AspNet.Mvc -Version 5.2.0
There are no dependencies of newer MVC versions on older ones, they are simply a newer version of the set of dlls, so there should be no issue removing older versions.
There are no dependencies of newer MVC versions on older ones, they are simply a newer version of the set of dlls, so there should be no issue removing older versions.
Are you sure???
NuGet decided to upgrade an MVC 4 to 5 box and it hosed the solution. Right now, I have this problem:
access method 'System.Web.Http.HttpConfiguration.DefaultFormatters()' failed
But, any solution found on the web right now has not worked.
It seems Microsoft is back to the ol' marketing tricks, bundling crap galore and creating an evangelizing environment where those using their technologies spend an inordinate amount of time on THEIR technologies, not the end solutions. I'm so frickin' mad that if my solution doesn't start working soon I'm tossing Asp.Net MVC after using it for four version with ZERO problems like this and going node.js.
I am using EF 4.0, at the time I am writing these lines I heard that EF 4.1 update 1 has been released and EF 4.2 is in beta. From wikipedia
A refresh of version 4.1 named Entity Framework 4.1 Update 1, was
released on July 25, 2011. It includes bug fixes and new supported
types.
But I only found a link of Version 4.1.10311.0 from Microsoft which date published is 3/21/2011. So I wonder if version 4.1.10311.0 is the latest release so far. If it's not, where can I download the latest release ?
ps : For some reasons I can't use live update, I need to download package to install manually.
From Arthur Vickers:
What if I can’t use NuGet? What if you can’t connect to the Internet
from your development machine. Or what if you are not allowed to
install NuGet on your machine. Don’t worry; all is not lost.
First you need to get the NuGet package. For this you do need to be
able to connect to the Internet from some machine—but it doesn’t have
to be your development machine. You’re reading this so presumably
you’re not completely off-the-grid. :-)
You can get the package by using NuGet in Visual Studio on a machine
connected to the Internet in the normal way—just install the package
you want into a dummy project. After installing the package you can
find the .nupkg file either in the dummy project folder or by browsing
the Package Cache from the Package Manager Settings menu option.
You can also get the package without Visual Studio by using NuGet.exe.
If you are able to install NuGet on your development machine then do
so and setup a local feed. This may sound daunting but it’s really
easy. Copy the .nupkg file to your local feed and then use NuGet to
install it in the normal way—with no connection to the Internet
required.
If you can’t install NuGet on your development machine then take the
.nupkg file and rename it to .zip—yep, it’s a zip file. You can now
extract EntityFramework.dll from the zip file and use it as you would
any other assembly. Note that you will not get any of the automatic
project-level integration I mentioned above, so you may have to do
more manual configuration of your project.
If you are using EFv4.0 you mostly don't need EFv4.1 or EFv4.2. Those versions bring new type of mapping (code first / fluent) and new DbContext API which can be used instead of ObjectContext API. So unless you want to start a new project with those "new" features or completely migrate your existing project you don't need it. Real new functionality for you will be included in .NET 4.5. DbContext API and code first is shipped only as NuGet package since EFv4.2.
use the package-manager in VS2010 to install
Tools + Library Package Manager + Nuget package manager
EF 4.2 has just been released: http://blogs.msdn.com/b/adonet/archive/2011/11/01/ef-4-2-released.aspx
This is a minor update over 4.1.
The runtime components are available via NuGet. The designer etc. updates for VS are a separate install.