I have a ASP.NET web app (.NET 3.5 SP 1) compiled on a Windows XP x86 (32 bit) box. The app currently runs on a Windows 2003 (IIS 6) server. I'm planning to move the application to a Windows 2008 R2 (64 bit) server. I was wondering if anyone has had any experiences with a similar migration? Does a x86 ASP.NET web app work out-of-the-box on Windows 2008 R2 (IIS 7.5)?
Cheers :)
Rowan
You should be able to make the transition with minimal work. We did it before. We can talk offlist if you'd like, lemme know.
You shouldn't have too many problems - we build and develop on XP x86/IIS 5.1 and deploy to a 64-bit Server 2008/IIS 7 platform. Just make sure you've got a staging environment to test on (even if it's just a Windows 7 installation for IIS 7).
Related
i'm getting started with asp.net vNext and i've found something that i cant understand if is a limitation on the DNX or if is something still not fixed.
When i'm publishing a simple webapi, as simply as the the default VS2015C template, my IIS 7 says:
IIS 7.5 or higher is required.
Is there some workarround or is really a limitation?
According to the latest community standup, the HELIOS integration between IIS and asp.net 5 was stopped. Ongoing the only server provided by MS is kestrel. You have to start and integrate kestrel into IIS by reverse proxying it.
This is quite normal in the Unix world and the .net team had to reduce the maintenance effort here.
Answering your question: Considering the Announcement I think practical usage in an Windows Environment via HttpPlatformHandler is only possible IIS8+.
ASP.NET 5 never has and never will support IIS 7 (Windows Vista and Windows 2008 both have IIS 7 only); IIS 7.5 and higher is actually required to bootstrap the dnx. If you want to work with ASP.NET 5 you must be running a Windows 7 or higher client OS or a Windows 2008 R2 or higher server OS.
I have created program using MSVC++ that besides it's main task calls WCF server functions. Under Windows 7 and Windows 8 everything works fine and I got several problems with Windows XP:
On some machines I have error that webservice.dll is missing and program doesn't starts. Why some Windows XP installations contain webservice.dll while others - not? How to install required dll?
On Win XP computers that has webservice.dll sometimes programm just crashes without any reporting. After recompiling program without WCF client code program runs fine. What might be starting point to look for the problem?
Windows Web Services API (WWSAPI) is an operating-system component of Windows 7 and Windows Server 2008 R2 or later versions of Microsoft Windows.
On Windows XP you need to package it with your app. The reason it works on some boxes is probably caused by one other installed application that uses that the WWSAPI as well.
The final version of the Windows Web Services API for Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2008 is now available
In contrast to the past pre-released version of this API, this final version release can be used in production code and redistributed with the final versions of the product. Because of this, the final version is only available to companies who agree to terms of Windows Master Redistribution License Agreement (MRLA). To acquire the redistributable installers for this release and a copy of the Windows MRLA for review, please email a formal request.
Partially copied and adapted from Windows Core Networking blog, from Ari Pernick, dated Oct 9th, 2009.
Is it possible that can I use Sharepoint server as development machine also. My mananger has asked me to use one of the newly purchased server for Sharepoint server as well as sharepoint development.
In future we will do some small development so what type of installation do I need?
Please guide me for the following which one I should install or which one is not required.
Standalone or Farms
VM
SQL Server 2008
VS 2010
SharePoint 2010 can run on a 64-Bit Windows 7, as per instructions from Microsoft.
It does not work on 32 Bit Windows as SharePoint 2010 is 64-Bit only, and it does not work on Vista.
Yes, it is possible to use your SharePoint server as a development machine. I'd suggest using a VM as it allows you to quickly and easily switch between, revert and deploy setups should something go wrong (and things WILL go wrong with SharePoint).
At work, my machine runs Win Server 2008 and I remote into a Hyper-V hosted VM which itself runs Server 2008 - I develop and run SP on that VM. Since I have SP, SQL Server and VS2010 all running on it at the same time, I allocate the VM at least 5.5 GB of memory (and it's still hungry for more).
You can develop for SharePoint 2010 on a Windows 2008 Server x64 or on a Windows 7 64bit. A Windows 7 is of course only recommended for development.
Most developers use a standalone machine for their SharePoint 2010 development. Creating a farm is complex and $$.
Personally I develop in virtual machines. I have on clean vm image that I copy for every new project (client). You need a powerful computer to run these virtual machines. At least 4GB memory and a recent multicore cpu.
You will need Visual Studio 2010, SQL server and ofcourse SharePoint. Office can also be handy but is not needed. SQl server express is included in Visual Studio and the SharePoint install also installs SQl server if needed. Certain Visual Studio versions include an "SQL server developer" license.
When Windows Server 2008 R2 was launched, the "server core" edition started to become useful to me, because it lets me deploy .NET background applications isolated on their own virtual machine instance with only a small fraction of all the disk space overhead of a default Windows Server installation, and very few Windows Updates. It comes with a subset of .NET 3.5 SP1 integrated (as an optional feature).
Now that .NET 4.0 is released, the redistributables explicitly state that it's not support on Server Core. Any chance that there will be a separate download available for Server Core (e. g. without WPF) any time soon, has anybody heard about it?
Since 2011-02-21, it is possible to run .NET 4.0 apps on Windows 2008 R2 Server Core. To enable .NET 4.0 support, you need to install Service Pack 1 and the .NET 4.0 Standalone Installer for Server Core.
Anything I have read says no. I would imagine that this will change but unfortunately it doesn't look like it will be soon.
I have a windows application that acts as a WCF Service that I developed on a 32bit Windows Server 2008 box. I have tested the application and everything works fine when running it from my development machine, as well as from my 32bit workstation. However, when attempting to run the application on a 64bit Windows 2008 Server, the application does not run, and a Windows Error Report is generated stating that the application stopped working. I have attempted to build the application on my 32bit Development Workstation, targeting both x86 and x64, to no avail. The only time I can get the application to run is if I comment out the code that starts the WCF Service. So my question is, do I need to dev and/or build this application on a 64bit workstation to allow the application to run on a 64bit machine?
Ok, I figured it out, nevermind...needed to run the app as admin on that server...
You need to configure http.sys to accept your urls using the httpcfg utility. There is a similar thing for Windows Server 2003.
How to add a URL ACL and avoid AddressAccessDeniedException in Windows Vista
Httpcfg Examples: Internet Information Services (IIS)