Installing and running visual studio executable on an Apple computer - windows

I am debating creating a simple project through Visual Studio on a Windows computer for a couple of my friends. However I know that a couple of them own an Apple computer instead of Windows. I was wondering (before I get to far) if it is possible (without installing other software like Parallels, etc) to install my executable so they can use it along with the supporting database structure (open to anything free or comes with Visual Studio) on their Apple computers?

You won't be able to do that without extra software. However you don't need to run Parallels with a full install of Windows.
You can try CrossOver. It lets you run Windows applications within OS X. I've use it a fair bit to play old PC games from my childhood. Works well.
http://www.codeweavers.com/products/

Related

How to develop Windows app on Visual Studio for Mac

I recently bought an iMac in order to develop my App on Visual Studio for Mac in a better environment (lots of issues on Windows), but on the Visual Studio for mac, there is no UWP projects.
It is understood that I have to create a new .NET project, but what are exactly the steps to follow in order to achieve that correctly for the app to work on Windows with a peace of mind? Should I have gone with Visual Studio code, which support the .NET core framework completely?
I saw on other answers that I need the .NET SDK tool, and so forth, but further details are needed if you don't mind on the why (not the installation stuffs, only the tech savvy explanations for the app to build correctly at the end!
You will need to run a Windows installation (eg, via Parallels or Boot Camp) and then run the Windows version of Visual Studio to create UWP apps.
You can do a lot of the business-logic coding inside Visual Studio on MacOS, but you will need Visual Studio and the Windows SDK to use WinRT types (which are required to build a UWP app) and to correctly build / package the app for deployment.
.NET is a big ecosystem. As you cannot develop all kinds of .NET projects using Visual Studio on Windows (Xamarin.Mac for example), you cannot do the same using Visual Studio for Mac (like you found, WinForms/WPF/UWP and so on). Such limitation comes from vendor SDK availability or other underlying systems.
In your case, you can easily develop web apps, Mac apps, and iOS apps. If you do want to develop Windows specific apps, like the other answer shows, please use Windows.
You mentioned ".NET SDK", but I believe that should be ".NET Core SDK". .NET Core apps are cross platform. Thus, you can develop such apps in Visual Studio for Mac, and then deploy to Windows. However, so far only console apps and web apps can be developed. What might happen in the future is still to be determined.
Visual Studio Code, however, is just a code editor. It won't give you extra flexibility.
For those whom imperatively needs to develop their app on all platforms, here is what I did, and the pros and cons:
Buying an Imac, thinking that I could also develop UWP projects within it
After realizing that I couldn't, I bought a cheap Windows 7 pro License on ebay (around 5$), and installed it on VirtualBox.
From there, I upgraded to Windows 10 for free and installed everything. It worked like a charm.
Cons: Buying a brand new IMac while a Macbook pro would have been better. An old one even since YOU CAN'T upgrade the ram.
Working on 8go of ram computer when you must give 4go of RAM to your VM isn't quite great. 4go gets you a laggy environment! Really frustrating.
So, prefer something older, but up-gradable (a cheap Macbook pro with 16go of RAM would do).
Not to mention that you will have to install Ubuntu as another VM in order to setup a .Net core Server for the majority of you.
What environment to favor while developing, most importantly when you are a C# and Xamarin noob like me?
The best being to develop from Mac as you will have FAR LESS ERRORS AND BUGS than in VS for Windows.
Correcting mistakes is really daunting and the best is really to develop from Mac to mitigate the damages, but it won't be hurdles free as well!
It took me more time debugging than coding within VS Windows.
After developing chunk of your app within Visual Studio MAC, the best is to get the code on the windows machine and arrange it to work in UWP.
UWP apps compile fastly and like a charm, so better is to get rid of errors within macOS, IOS, Android, and then go and adapt to UWP. This is easier IF YOU THINK ABOUT CHOOSING THE CORRECT LIBRARIES (working on all platforms, hence check my last advice).
From VS Mac, compile using macOS as a host! It's the easiest way to develop fastly, and correct your bugs.
Here is an article on how to get started from Mac:
https://blog.xamarin.com/preview-bringing-macos-to-xamarin-forms/
Cons: Always having to commit the code for it's use within UWP. But that's also a good way to save your project as well, so that if you screw up (like it happened to me numerous time) you roll back.
Hope that helps others whom didn't know what to do and where to start.
ALSO:
Don't follow tutorials dating from before 2017. Use the .Netstandard/.NET Core framework to develop your App so that libraries are more portable (following the blog article above should do).
Otherwise, headaches ahead!

Installing VS2005 on Windows 7

I'm trying to install Visual Studio 2005 on a Windows 7 box but am repeatedly getting the same error. When I run the installer it starts to run then pops up with a message saying:
"A problem has been encountered while loading the setup components. Canceling setup."
Various suggestions has said that maybe the install is corrupted so I downloaded a fresh copy of the ISO from MSDN today, same issue. Another suggestion is that installing from the ISO may be the issue so I extracted the contents of the ISO to a folder on my HDD, same issue. I have also tried running the files as administrator and in XP compatability mode, same issue.
Searching for this issue the most common responses I've found have been about installing SP1, however I cannot get the base product to install and therefore cannot apply SP1.
Does anyone have any further suggestions as to what I can do to fix this issue and get VS2005 installed? If anyone wants any log files of any variety I am happy to supply so long as you tell me where to look as I'm not sure.
As for why I am using VS2005 and not a newer product, it is required for the ongoing support and maintenance of some older applications we manage. These cannot be easily migrated to a newer version of Visual Studio without some considerable investment of time and that would probably be longer than the time it will take to develop newer, replacement applications (which is currently in progress). Until the new applications are available though we need to maintain an environment to use.
Did you try running setup.exe in compatibility mode with Windows XP? Some discussion here on how to do this.
Another alternative since you alluded to having an MSDN subscription. Download Windows XP and install it into a VM. (If HyperV isn't already in installed with your Win7, you can add it from Control Panel->Programs&Features->Turn Windows Features on/off). Then install VS2005 from there.

how to run a windows application developed using Visual Studio 2010 in MAC?

A windows applicatio is developed in Visual Studio 2010 and teh database used was MS Access. Can i run it directly in MAC. i.e. using the EXE or do i have to do some setting or is it not possible at all.
You cannot run windows application directly in MAC OS at all! But there is such a enviropment like - mono, which allows to compile the C# and .NET platform solutions for other OS. Feel free to use google with query - Mono develop.
From my experience - Mono isn't stable and didn't work as fine as Visual studio.
No you can not.
EXE is a windows executable file format and thus don't work on OS X, linux or any other Unix based OS. As mentioned you can use parallels wich cost money. There is a free alternative called VirtualBox. This does not provide the same features, but you have to decide for yourself.
https://www.virtualbox.org/wiki/Downloads
http://www.parallels.com/eu/
Here is a guide to how you set up VirtualBox on your MAC -> http://www.makeuseof.com/tag/virtualbox-running-windows-on-a-mac-for-free-sort-of/

Shopping list for developing Windows app on Mac

Folks,
I need to maintain a C#/.Net desktop application. So, I need to set myself up with Windows(7?) and Visual Studio.
My current development machine is a Macbook Pro and I would like to continue using it. Overall, I am considering the following recipe:
Install VMWare Fusion or Parallels or VirtualBox for running the Windows OS
Buy a version of Windows to develop on
Buy Windows Developer tools
Having been in the open source universe all this time, I am utterly unfamiliar with the options/packages in the Windows world. I could use some help on the following:
Does the recipe above look fine, or do I need to change something?
What is a good VM environment to buy/use? VirtualBox is free, but Parallels/VMWare promise Windows app that blend in with my Mac windows. Could use some help on this topic
Does MSFT sell a package deal which has bare bones Windows 7 and the necessary dev tools, or do I need to buy the OS and dev tools separately?
Since I only need Windows to churn this C# desktop application, What is the OS version and flavor or Visual Studio I should get?
Thanks in advance for any pointers.
-Raj
* Does the recipe above look fine, or do I need to change something?
Looks fine to me, it is what I do too.
* What is a good VM environment to buy/use? VirtualBox is free, but
Parallels/VMWare promise Windows app that blend in with my Mac windows.
Could use some help on this topic
I've used parallels and VMware fusion and I prefer VMware because I can move machines to other VMware hosts relatively easily. They seem to flip-flop when it comes to performance, but I think this week, Parallels is a little faster (of course this might change with the next fusion update, or the next parallels update).
* Does MSFT sell a package deal which has bare bones Windows 7 and the
necessary dev tools, or do I need to buy the OS and dev tools separately?
I think that this depends on what you are doing. If you purchase an MSDN subscription, you get software that you can use for development (including all windows versions). But if you just purchase Visual Studio, then you need to buy the OS too.
* Since I only need Windows to churn this C# desktop application,
What is the OS version and flavor or
Visual Studio I should get?
You should get whichever OS versions you intend to support your application on.
Good luck,
--jed
Doesn't a Mac have Boot Camp? If so, use that.
It looks fine though. You must buy the OS then the Dev tools (There's Visual C# Express for free though). I would get Windows 7 and either the newest Visual Studio (2008, but 2010 is being released on April 12).
I've used both Bootcamp and VMWare Fusion with 15" MacBook Pro for quite a while (2013 and 2018 models). Bootcamp is better in terms of battery life. Though in terms of performance, Windows VM under macOS can be a better dev box due to significant difference in SSD performance - it's way faster in VM rather than in Bootcamp, especially in random reads/writes (which is crucial for project build time).

How clean is uninstalling the Service Packs from Visual Studio 2005?

This is a total dah question but I hope somebody can help me out.
I have VS2005 SP2, nonetheless, I really need to use VS2005 No-SP to compile the release version of our product. Is it "safe" to uninstall the service packs?
What I mean by this is:
What implications should I take into consideration?
Will be things left from either Service Pack that might invalidate my requirement?
Would it be better to uninstall VS2005 and everything and then reinstalling it?
Should I rather format my computer and install VS2005?
Sorry for not directly answering your question, but might I suggest using virtual machines for your 'special' development scenarios?
In our office, people who get new machines, or for whatever reason find themselves doing a clean install are installing Windows 7. As such, they really don't want to pollute their clean 7 installation with our legacy development tools because of the occasional need to update one of our legacy applications.
Instead, they use a Windows XP virtual machine into which they install our legacy development tools. Having these special-situation development VMs saves so much time. (Testing in general is so much easier with VMs, too!)
A nice plus that makes working with these VMs is the "Unity" feature of the latest version of VMWare Workstation (6.5.) If you're not familiar with Unity, watch http://www.youtube.com/watch?v=B4PYg9WkSLc It's very handy being able to have your virtualized apps appear to be a part of your host OS.
Since it seems that your actual problem is the dependency on the CRT DLLs, you should look at the _USE_RTM_VERSION macro. There are corresponding macros for ATL and MFC.

Resources