here is a brief what I am trying to achieve.
I am working with an application which is in WordPress and running on Apache and in one of the screen (page) it's require to use any already built module which has a large set of functionality built in .Net, that require an IIS support.
I am running WordPress application on Linux and not sure if Linux provide that flexibility to run both servers Apache and IIS at the same time.
Have gone through with some blogs but nothing yet, not sure even it's possible or not.
Any suggestion would be appreciated...
Not is possible run IIS over linux, you can use kestrel with netCore ,because IIS not is cross plataform, many applications that run "net framework" you can migrate to "net standard" , one option is install "docker windows machine iis" but only run in windows machines
Related
Is there any safe way to host a site Net core website through a installer (may be in IIS), similar to any desktop application installer?
e.g. Neo4j works as webservice but has its own jetty server to host. U just download and its up and working.
I dont understand your problem. Why you just dont run your app with Kestrel? (dotnet <patch_to_your_dll)
I have Worklight Server and Appcenter installed on RHEL 6.4 and am unable to find commands to start & stop these servers gracefully. Primarily, I would like to do this to apply patches, make changes to databases etc.. Any help is really appreciated.
It sounds to me like you are referring to installed instances of Worklight Server and Application Center in a QA/UAT/Production environment.
This means that your Worklight Server and Application Center instances are deployed to some application server (either WAS, WAS Liberty or Tomcat). So the way to start and stop these instances would be via the commands available by the the used application server. You should probably then consult with the user documentation of the used application server for the commands. For example for Liberty: http://www-01.ibm.com/support/knowledgecenter/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_admin_script.html
If you are in fact referring to the Worklight Development Server (Worklight Studio plug-in for Eclipse), there is no publically available way to stop the server from command line -- unless you are using the CLI tool to manage your development (working outside of Eclipse), there you do have a command for it.
Wondering if I should stick with testing on my local IIS install or just use the Express version. Any reason why or why not?
generally, I would try to have the development / testing environment resemble your live environment as closely as possible.
so if you're using IIS in production, I'd recommend using it in development also.
I cannot tell you how many times I've seen web apps working perfectly on the development machine using IIS6, and crashing completely on IIS7.
I suggest this configuration:
IIS Express on the developer machine
same IIS as in production on a staging machine
IIS Express is the best choiche on your local computer because it's easy and fast to install and configure and doesn't require administrative rights to be installed.
It's completely integrated with Visual Studio and it has all the functionality of IIS.
And the configuration is in the source code repository so each developer can checkout the solution and is able to run it with minimal effort.
As sJhonny suggests is recommended to have an environment closer as possible to the production environment.
The best way is to have a staging server with the same software configuration of the production server, in your case with the same IIS complete version (it's enough a virtual machine).
I'm jumping into updating a Classic ASP web app coming from a PHP background and am trying to get my bearings. I'm used to just installing something like MAMP, messing the httpd.conf a bit and getting on my way.
Ideally, I would like to be able to edit this app completely locally on my Macbook Pro running OS X Leopard so that I'm not messing with my client's server too much. Now, if I need to I'm willing to install Windows 7 via Boot Camp or running it as a virtual machine. Of course my preference is to stay completely in OS X, but I have my doubts about that possibility. So, how should I go about this?
One thing to note is that once I'm done updating this ASP web app I will have to make changes to a VB(.NET) application as well, so I'd like to have to change my virtual workspace as little as possible when that time comes around.
As you say, you will need to install Windows via Boot Camp or VM (your choice).
Once in Windows, you can install Visual Studio 2010 (Express free), where you can edit your ASP Classic files, and you will have it already installed when you need to do VB.net
Do not forget to install IIS when you install Windows (you will need it to run ASP Classic)
My development machine is running Windows XP SP2 (and IIS 5.1 by implication).
Until recently our deployment environment was based around Windows Server 2003 (and therefore IIS 6.0).
We are about to move to Windows Server 2008 (and therefore IIS 7.0) for a new project.
Our projects use ASP.NET MVC and WCF Services.
Are there any key reasons for us to upgrade our development machines to run Windows Server 2008 (or possibly Vista, since this also comes with IIS 7.0)?
I would say it's in your best interest to upgrade your development machines to emulate as much of the production environment as possible within your means and resources. Otherwise you may fall into traps you're completely unaware of just by deploying an application from your development machine to the server's environment, which may pertain to differing versions of IIS, the version of .NET framework each machine is running, or just the way the code is compiled or executed at runtime.
Especially since IIS 7 has been vastly upgraded since IIS 5.1, why shouldn't you work closer with it's current functionality while developing before you missing out on some great opportunities? To really know what to expect from an application in production, develop it under the same circumstances.
Edit/Added: This link may help you see at least one significant example of how differing versions can affect your project.
I would recommend that you develop against the same major build as you intend to deploy on. That said, this leaves you with a few options. First, you could build against your local IIS installation (as it appears you currently do). That means that all of your boxes should likely be upgraded to Windows Vista or Windows 2008 Server (or Windows 7 as it is running IIS 7.5). Your second option is to deploy to a remote machine. It is entirely possible to deploy your application to a remote test machine running IIS 7 and remotely debug as well. The problem is that if you have more than one developer working on the remote site, it becomes problematic. IIS can handle the remote debugging on different webs for different developers, but depending on your architecture and configuration, you may still be sharing resources between instances of test web applications.You could occasionally deadlock each other. The only benefit is that you don't have to buy licenses for all of your machines (and potentially upgrade hardware to support the OS upgrade). However, I think that would be short-sighted. The loss of developer productivity wouldn't be worth it, IMHO.
There are major changes between IIS 5.1 and IIS 7.x. The changes to the architecture, such as the integrated pipeline, can result in drastically different behavior and compatibility issues. I think you will find that IIS 7 far more developer-friendly. The introduction of things such as failed request tracing, extended logging, and enhanced error pages alone make it much easier to track down errors in your application. In that regard, the upgrade is well worth it.