I have a macbook M1PRO, and I need to debug .net2.0 and .net 3.5 codes in its Windows11 virtual machine, but I can't set up a code runtime environment。
I have installed .net framework 3.5 in the "enabling or disabling windows features" in the control panel, but its existence is still not recognized in visual studio.
enter image description here
enter image description here
If I don't use a simulated x64 virtual machine or another x64 computer, I just want to run all programs on one computer, how can I solve it？
If you create a x64 VM, then you have to install windows 11 (not arm based version).
then install visual studio for windows. (again, the non arm version).
At that point, you can develop with .net framework 2.0-4.8.
You can't create, run, use, enjoy, develop .net framework asp.net applications unless you running a windows VM, and using the windows version of VS.
You can ONLY run (and develop) .net core applications on arm based, or other computers, and NOT .net framework applications.
given that you looking to develop (or work on) a x64 .net framework, and quite a older version?
Then you have to create a x64 (not arm) based VM, and install the x64 bit version of windows (again, NOT the arm based version of windows). You then install Visual Studio for windows.
The above will thus allow you to develop and work on .net framework applications, such a as asp.net .net framework based application.
Related
I currently have an Ubuntu 18.04 environment. For our course, we need to have Visual Studio, ASP.NET, Microsoft SQL Server and IIS installed. One solution was to install the Windows OS on VMware/VirtualBox, but since Windows OS on a virtual machine is a bit heavy on my laptop, is there any other slightly "light" OS that allows me to install the 4 requirements already mention?
As Lex Li says the IIS is Windows only,VS is only available on Windows and Mac. So you could only use the windows.
Here is a workaround, if you are familiar with the VS code, you could use VS code develop asp.net application, then you could use docker to run the asp.net application with IIS.
More details about how to use vs code in the linux, you could refer to below article:
https://code.visualstudio.com/docs/setup/linux
About how to use vs code to test application with docker, you could refer to below article:
https://medium.com/#agavatar/working-with-docker-in-visual-studio-code-756ea8b32abc
Since I am planning to buy a new MacBook Pro (2017) and currently working on a Windows 10-device on a ASP.NET MVC (Not ASP.NET Core MVC) project for my internship, I was wondering if it is possible to continue developing the same project in Visual Studio for Mac.
To put it in other words: Is it possible to develop ASP.NET MVC applications in Visual Studio for Mac?
I tried to Google this, but I could only find ASP.NET Core MVC projects being discussed for VS for Mac. The current project is NOT a Core project, but just an ASP.NET project.
I really don't want to install Windows either on my MacBook Pro or on an external drive.
As you've correctly surmised, it's not possible to build ASP.NET MVC projects on the Mac that aren't based on .NET Core or Mono. So if your project is currently targetting ASP.NET on .NET Framework 4.x, the you'll either have to stay on Windows:
Use Bootcamp to run Windows on your Mac
Use a Virtual Machine to run Windows inside Mac
Use Parallels Desktop or VMWare Fusion to run windows applications inside your Mac
Or you can convert your application over to Mono or .NET Core, depending on your dependencies that may be relatively easy, or very hard or anywhere in between.
You could also decide to use Visual Studio Team Services to build your code on a Windows Hosted agent and edit the sources on yoru mac, you'd have to forego the ability to compile or run your code locally.
You can also decide to "rent" a virtual machine in Azure (maybe your have MSDN credits you could use for this purpose?) and remote desktop to that machine to work on your project.
I am developing .net applications on a mac using parallels where I have a windows VM and all my .net tooling.
now that visual studio 2017 can run on mac, would i be able to eliminate my method and run visual studio direct on my mac and seamlessly be able to move my code over to the mac version and compile and develop asp.net web applications?
I am only worried about web applications.
I have been playing around deploying my .NET Core application on several Operating Systems using self-contained and portable platforms.
As expected, this runs fine on Windows 8.1, Windows 10 and OSX.
I also have a 2008 Windows Server with IIS7 and this is causing a few issues. I have tried to run the self-contained executable but returns procedure entry point kernel32.dll error which apparently means that I have selected the wrong runtime in my project.json file.
Where can I get a list of compatible ASP.NET Core runtimes?
I believe portable .NET Core apps are NOT compatible with IIS7 as AspNetCoreModules requires IIS7.5, is this correct?
The article Publishing to IIS on ASP.NET Core docs says that Windows Server 2008 R2 is required.
Going to .Net SQLite (System.Data.SQLite) download page, there is different editions for each .Net framework and CPU architecture (32/64). I have a WPF/NHibernate application that works on my machine fine. My machine is Windows 8 x64 with .Net 4.5. Application is in .Net 4.0 and I used SQLite x32 for .Net 4.0 in it.
Problem is when application is deployed to customer's machine. Some of them have Windows XP, some have Vista and some have Windows 7 and 8. Many of them can not load database driver and I am forced to use another System.Data.SQLite. For example a x64 or a .Net 2.0 on them. I wonder why this happens and how it can be corrected. Specially when all customers have .Net 4.0 on their machines.
Any help is appreciated.
As this page explains, System.Data.SQLite assembly binaries for the .NET Framework 2.0 should work with the .NET Framework 4.0, but the reverse is not true. So if you need backward compatibility with older versions of the framework, you should use the older 2.0 assemblies.
There are other intricacies, such as how to properly use the Mixed Mode assembly with x64, so you should read that page carefully.