I suppose this is more of a question of whether the VB6 Runtime runs on Windows Server 2012 R2.
I was thinking about Azure app migration scenarios, and Azure RemoteApp could be a great way to allow an enterprise to migrate to the cloud and Windows 10, while still supporting their legacy LOB applications; such as those written in VB6.
I wasn't able to find any information in the Azure documentation specifically on this, so I thought I'd ask it here.
Does anyone know if a VB6 app can run in Azure RemoteApp?
It seems that perhaps VB6 apps did run in Azure RemoteApp, but this is no longer really relevant, right? Long live VB6! :)
Related
Having being unsuccessful to find a decent resource I am finally asking it over here. I have a legacy .Net Frmework Windows Service (which is now migrated to .Net Framework 4.7.2) which I want to eventually migrate to Azure PaaS. After looking around I found 3 ways I could do that and not counting the options like hiding it behind a web app hosted in IIS because I do not think that is the correct solution. I think the correct ways are:
1) Use Worker Role: This is provided by the legacy Cloud Services platform and due to its slow deployments and staging costs is out of question.
2) Use Web Jobs: It may need code changes but I am unable to find a decent article or tutorial in the context of windows services.
3) Use Containers: This seems to be the solution most suitable but I want some expert to guide me through it as I am completely new to docker and azure. Since the service is in .Net Framework, the target OS could only be Windows Server Core(https://learn.microsoft.com/en-us/dotnet/standard/modernize-with-azure-and-containers/modernize-existing-apps-to-cloud-optimized/deploy-existing-net-apps-as-windows-containers) but when I pull the image I get the message that it "cannot be used on this platform". I am using Windows 10. Does this mean that I need to be working on Windows server family OS to be able to pull image which effectively means that to be able to deploy .Net Framework application in an Azure container, I need to be working on Windows Server OS.
Links to a few good reads or videos are welcome as I am unable to find may be because I am not searching it correctly. I would imagine that windows service migration to Azure is a common scenario but I may be wrong.
Do follow the steps mentioned here
,
https://github.com/dotnet-architecture/eShopModernizing/wiki/02.-How-to-containerize-the-.NET-Framework-web-apps-with-Windows-Containers-and-Docker
Also for your windows service, you do have a couple of other options as well
1) Convert your app into an Azure Function and run it on timer trigger. But your app must complete execution within 5 minutes.
2) Deploy your app as a timer triggered web job.
i have a web application which is created using .net framework 2.0 which is running on windows server 2003.is it possible to migrate that to Microsoft azure.if so does it require an entire rebuild on azure?
A really useful utility for this case is Azure Migration Assistant.
https://azure.microsoft.com/en-us/downloads/migration-assistant/
It will check all your IIS sites and show you if it can be moved up to an App Service, checking target framework, port bindings, etc.
If everything is ok, it can do the migration for you.
Worst case scenario, you can move your application to Azure inside a VM.
It depends on what you mean by "migrate".
If you think about moving as is, you have an option to choose IaaS, where you'll just get a VM and do what you want on it. That'll give you both full control as well as full responsibility over your app.
Otherwise, if you want to avail of the PaaS offering, you'll have to make minor tweaks to your application (assuming the framework version is supported).
I was wondering how can I use Epicor 10 in Windows Azure.
I want to install the app server on Windows Azure, all the Epicor 10 components, when it's all done and ready, I would like to use normal PC's to conenct to the app server[Windows Azure], download Epicor Client and use it on the client PC's.
Is there any way to achieve this?
Thanks a lot for your time.
This seems like a reasonable setup to me. Epicor 10 hosted on an azure vm should work similarly to an install on a conventional server. Here is some microsoft documentation on creating azure vms: http://azure.microsoft.com/en-us/documentation/services/virtual-machines/
For a standard install, you should follow the microsoft tutorial as necessary along with the specifications set in the Epicor 10 hardware sizing guide (apply this to your vm creation) and Epicor 10 server implementation guide available on Epicweb.
You're probably aware of this if you're already in process for implementing E10 on Azure, but for preliminary concepts of Epicor on Windows Azure and explanation of Epicor working on azure, there's a presentation which is useful for slides 17-20ish and 37: https://epicweb.epicor.com/resources/MRCCustomers/Embracing%20the%20Cloud%20-%20Leveraging%20the%20Microsoft%20Azure%20Platform%20to%20Evolve%20your%20Business.pptx
You'll have to login to your epicweb account.
i am not sure if this is the correct place to put of this question as this has nothing to do with coding but rather configuration. My apologies.
I want to hook up my visual studio 2012 profiler to a azure service WaWorkerHost.exe which is hosted on Windows Azure.
After much searching i found Profiling Cloud Service. But this shows only how to profile WaWorkerHost.exe which is currently running on localhost i.e. on Azure Simulator rather than on actual Cloud.
Any help will be appreciated.
Thank you
Not sure if this is something you're looking for, but you can enable profiling when you publish your cloud service through Visual Studio.
and here's a link which talks more about it: http://msdn.microsoft.com/library/hh369930.aspx.
What type of projects/software applications are suitable for Azure and why?
Thanks
Rather than thinking of what can be supported in Azure, it might be more helpful to think about its challenges as you decide to port your app over:
Web applications. Since a Web Role hosts IIS, you'll generally have little issue porting a general-purpose asp.net or asp.net mvc website to Azure. There are some glitches you'll run into - see my related answer for more details.
UI. If your app has specific output similar to a WinForms app, you won't be able to run it since you have no video output.
GPU dependencies. If you're doing some background processing dependenton a specific GPU, you won't be able to run in an Azure VM.
Registry and other system-level access. If your app needs to update the registry or run an MSI, you won't be able to install your app.
Instance affinity. If your app requires session stickiness (e.g. a logged-in user MUST visit the same server instance with each access), you won't be able to accomplish this.
COM interop. COM interop is very limited, since you can't install anything via the registry. If you rely on Excel Services, you won't have that capability.
SQL limitations. SQL Azure is limited to 50GB today, and offers no ability to custom-tune the server instance. Also, while it does support a big subset of SQL Server, it doesn't support 100% of SQL Server, so it's possible some of your sprocs may no longer work. There's no SQL Agent today, so you'd need to recreate that functionality in a worker process.
That's just a quick braindump of some challenges you might run into - I'm sure there are others.
Just keep in mind that Azure is providing Windows 2008 Server images for your app to run on, so if your app can run in that environment today, and doesn't require things I listed, you should be in pretty good shape.
You can make most of the .NET projects working in Azure. Azure has support of following project types: web site (both ASP.NET and ASP.NET MVC), worker (background application) and wcf service.
Don't forget security too - there's various ways of authenticating onto Azure but none are as simple as just setting IIS/ASP to windows auth.