So I'm new in the Visual Studio 2015 (Community), I liked the C# + XAML set so I start learning from scratch (I'm a VB6,Php,Js Dev) and I found the following issues.
a) How do yo do a standalone installation or release of a simple application?. (When I build the release it says: this application can only run in the context of an app container).
b) By programming on this set (c# + XAML), can I build applications for WinXP,Win7,Win8? (I found that the only requirement is to have .NET 4 installed, and when creating the solution on vs2015 target that framework).
I'm used to the fact that I can build my app and it will run just by installing the dlls on the client machine.
Thanks in advance for any answer or directions to solve this questions.
It sounds as if you have created a Modern app project. That will only run on Win8 and later.
If you want to use C# along with XAML, you should re-create the project as a WPF Application. When you create a new project, you would just look under the "Windows" section. Do not select "Universal" or "Windows 8" unless you intend to build for newer systems. WPF projects can be run on WinXP and later. I believe WPF also has a minimum requirement of .NET 3.0.
Related
Can a project made in Visual Studio for Mac be opened and run in Visual Studio on Windows?
I only have access to Mac, so unfortunately I cannot check it by myself.
It depends on the framework and libraries you target. Obviously if you use MonoMac or something with a Mac-specific UI, it'll run only on the Mac, but if you're writing a console app targeting .NET Core, by default it'll run fine on Windows. To write a cross-platform UI, you could try a third-party framework like Avalonia.
Edit: I should add that the .csproj and .sln formats used by Visual Studio for Mac are the same used by VS for Windows, so in general a project or solution for a cross-platform app (.NET Core) or library (.NET Core or .NET Standard) can be read by either Visual Studio.
In fact, I run Parallels with Windows 10 on my Mac with my repos in shared folders and will compile my cross-platform apps from whichever side on which I wish to run them. (There are line-ending considerations and other minor annoyances, but it works.)
I am writing a Windows Forms program which doesn’t use any new tech from .net framework 4.5-4.7, but unfortunately I started the project with .net Framework set to 4.6.2. (Because in the beginning the company told me they only want to use it on win 7/8.1/10, later they changed their mind)
I know Windows XP is obsolete, but I have to run this program on a XP machine as well.
I already tried to set the targeting framework to .NET 4.0, but when I try on the XP machine with a .msi installer, it throws an error, that I cannot run a .net 4.6.2 dependent program, even before it starts the install process.
Can I “convert” the whole project to .net 4.0, or I have to copy all buttons, textboxes, couple thousands lines of code, etc. to a new project which only uses .net 4.0?
I’m using Visual Studio 2017.
Looking at the log you shared I can see DIRCA_CheckFX so I'm guessing the setup project is a vdproj which has been deprecated in favour of a framework like WiX.
The CheckFX step is a launch condition which you should be able to delete/manipulate, by opening the project and finding the launch conditions:
View -> Editor -> Launch conditions
I am considering options for a new computer and I am debating between a Windows and MacOS platform. I'm a windows (C#/.net) developer and I work primarily in visual studio, but I also work in other open source technologies in my personal time.
Microsoft has recently released Visual Studio for MacOS and I'm wondering if there are any significant limitations that would make .net core in visual studio on a Mac too difficult to be worthwhile.
I've heard of some early limitations such as not being able to publish to the filesystem and not being able to run multiple instances of Visual Studio, but I'm unsure if these have been resolved, or if they are on the VS for Mac roadmap.
I am trying not to make this an opinion-based question so I am looking for factual limitations or benefits. One of the benefits I see is being able to develop software and test on all three major platforms via virtualization (mac, windows, linux).
You will be able to do on Mac
Run and debug .NET Core projects.
Run multiple instances of Visual Studio 2019.
Run and debug Xamarin projects.
You won't be able to do on Mac
Run ASP.NET Full Framework projects.
Run Winforms projects (you might if you use Mono, but it won't be transparent).
Run IIS.
Visual Studio for Windows has more project templates, especially for Azure.
Benefits?
Running .NET projects if you have a Mac.
I think Xamarin development is better on Mac.
Personal conclusion
I use both environments every day. If you are a Mac user is great being able to run .NET Core apps without a VM. But, I consider VS on Window way more mature than VS for Mac.
You may use JetBrains Rider on your Mac or run the Visual Studio for Windows under Parallels Tools.
There's probably a really quick and easy solution to this but I was not able to find it in search. In a nutshell, created a windows 8.1 desktop project a while back in VS2013 on windows 10. Had to rebuild the win10 machine. Installed VS 2015 this time around. enable develop mode, crack open the same solution (project targets windows 8.1).....but my only debug options are my installed web browsers. It's as if VS has it confused as being a web app. Everything in the property pages looks correct. Any ideas?
Create a new desktop project in VS 2015, and then use a tool like winmerge or other diff tool to diff the project/solution files (your real one and the new one). That should show you what is incorrectly making VS treat it like a web project.
It was just me being a numb skull. Hadn't worked in VS in a while, had added a couple web projects to the solution right before walking away from it last, forgot to set windows 8 project as startup project. smh {-_-}
How do I use Visual Studio to develop applications on Mono? Is this possible?
You just build the applications in Visual Studio, and run them under Mono instead of under .NET. The binaries should be compatible... but you'll need to make sure you don't use any libraries which aren't available in Mono - see the Mono Application Compatibility Guidelines.
(According to that page, you need to turn off incremental builds in Visual Studio though - a point I wasn't aware of before :)
See this article on how to run your apps while targeting the mono framework from VS.
Miguel has posted this entry a while ago, so it's quite dated. You can also try this and this (all hail Web Archive!)
Since version 2.0 MonoDevelop supports VisualStudio project/solutions file format. This means that you can use the same code base on Windows with VS and .Net and on Linux with MonoDevelop and Mono. That in my opinion is the best way to go about it. There are no major reasons to run application in Mono on Windows, other than for testing purposes and for that I'd rather set up a virtual machine to test the software in native environment.
I've posted an article on how to integrate Mono 2.8 (the build for .Net 4.0) into Visual Studio 2010 here - there's a link there to another profile built for Mono 2.4 (.Net 3.5) if that's what you're aiming for.
You can integrate the new Mono 2.8 profile with 3 simple steps:
Download the profile itself from here.
Unzip the contents of the profile Zip to one of the following directories:
32-bit systems: C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile
64-bit systems: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile
The "Mono" folder in the ZIP should be directly under the "Profile" directory.
Restart Visual Studio if it had been running, open the properties of the project you want to use with Mono, and select the Mono Profile for 2.8:
Note: You will not be able to select the Mono Profile straight from the New Project dialog box; for some reason, that list of profiles doesn't match. Create your project as a .Net Framework 4.0 project first, and after creation set the project properties to Mono.
If you've upgraded your MonoDevelop install to the latest version (as of today, anyway), this Visual Studio solution & Project file will open with no problem - no changes required at all.
If you encounter the problem that you need .NETFramework,Version=v4.0,Profile=Mono in order to run the application, the trick was to create registry key.
For running Windows 7 x64, it was: HKEY\_LOCAL\_MACHINESOFTWAREWow6432NodeMicrosoft .NETFrameworkv4.0.30319SKUs .NETFramework,Version=v4.0,Profile=Mono
I suppose for x86 it’s HKEY\_LOCAL\_MACHINESOFTWAREMicrosoft.NETFramework v4.0.30319SKUs.NETFramework,Version=v4.0,Profile=Mono
(Where v4.0.30319 would be the version of the current 4.0 framework installed.)
Yes, you can develop on Visual Studio and target Mono (Mono for x86).
Here is an answer I made on all the available possible alternative to compile against Mono on Windows. However, it's focused for Mono x86.
As a summary, let's list the possible choice for VS development:
MonoHelper addin
Mono Profile
For Android/Ios, you can also cross-compile and debug inside Visual Studio with Xamarin addin. Although it's not free for commercial huge applications, there a free version available to make small ones.
Note: For those who wonder why in the world I would like to develop in Visual Studio on Windows, instead of MonoDevelop on Unix, let say that developer experience in MonoDevelop does not compare to VS one (especially when it comes to debugger/refactoring, the last due more to Resharper than to VS itself).