Browse by Tags
All Tags »
IIS News (
RSS)
We have a new release of the RC1 build to fix a couple issues that people found. We recommend that folks download the new version as it fixes some important issues. How can I get the new build? Just go to our download links for x86 and x64 . How does it upgrade if I already have the earlier RC1 build? If you install the new build, it will automatically uninstall the older build and install the new one. How does it work if my server is running the old RC1 (437) and my client is running the new RC1 (438)? You will get an error that there is a version mismatch. The reason for this is that if your builds are out of sync, something might be different in the syncing process and cause an error. So we require the client and server to be running the same build. What issues were fixed? Installing an application package in certain time zones would result in an error. Skip and replace rules didn't work properly. A couple of other smaller infrastructure changes. Let us know if you see any issues...
The Web Deployment team is excited to announce that RC1 shipped this morning! We now have a release candidate that can be used for production testing and supports many new features. So what did we add, you ask? The biggest feature is our integration with the Web Platform Installer , or WebPI. Now you can use WebPI to seamlessly install community web applications DotNetNuke or WordPress on your machine including all of their dependencies such as IIS, ASP.NET, PHP, etc., using the Web Deployment Tool to perform the application install. You can even submit your own applications into the Windows Web Application Gallery so they can be included in WebPI! Beyond that we have a bunch of features as well as a lot of performance and stabilization work. Web application packaging and deployment additions: Added the ability to create packages by hand without requiring the Web Deployment Tool to be installed. Enhanced the iisApp provider so that IIS application packages can be installed on IIS 6.0 (Windows...
We briefly mentioned that Visual Studio 2010 is integrating the Web Deployment Tool, but we didn't really go into details. Here's a great blog post that covers the highlights of VS 2010 deployment features, not just MS Deploy, but a lot of other cool stuff as well! http://blogs.msdn.com/webdevtools/archive/2009/02/04/web-deployment-with-vs-2010-and-iis.aspx Read More...
The IIS team is proud to announce the latest release of the Web Deployment Tool Beta 2, which includes significant new features for both IT professionals and developers. In addition to our existing functionality of server synchronization and migration, but we’ve added web application packaging and deployment with integration with IIS Manager and the upcoming Visual Studio 2010! Because the Beta 2 release has brand-new functionality around application packaging not previously available, this release is not a production-ready or Go Live release. We will be changing and adding more functionality in the next milestone after Beta 2. Easily deploy, store and redeploy Web applications. The Web Deployment Tool enables you to package configuration and content of your installed Web applications, including SQL databases, and use the packages for storage or redeployment. These packages, which may include certificates, can be deployed using the IIS Manager interface without requiring administrative...
Just wanted to let everyone know that a bunch of us from the IIS and MS Deploy team are here at PDC 2008 in sunny Los Angeles! If you're here for PDC, please stop by the Windows Server 2008 Web Platform booth or check out our great talks on web deployment. We have some great news being announced and we'd love to meet folks that are currently using or interested in using the Web Deployment Tool. Happy deployments! Faith Allington, and the entire Web Deployment Tool team Read More...
Today the Web Deployment Team released the Beta 1 version of the deployment tool! If you're not familiar with the tool already, it is here to help you keep sites or servers in sync with IIS6 or IIS7, as well as migrate from IIS6 to IIS7. One of the key things we've worked on is the flexibility of the underlying framework, which you can see in the number of rules, the ability to configure dependencies and especially, the different providers that we support. You can sync or migrate not only the configuration of a web site, but also it's physical content and any SSL certificates. We also allow you to create your own manifest and define an application the way that you choose. Does your application depend on an assembly in the GAC? Or a registry key? These can be added to the manifest. Okay, enough about the tool, for everyone who has been waiting patiently for this latest release and given us excellent feedback in the forums, THANK YOU ! Please give the tool a try and let us know...
Let's suppose you are German, you developed an extremely cool web-site and now you want to make it available to your German Bier buddies. The only really fetzig site name you could come up with contains one of these nasty German umlauts: übersite.de (not registered at the time I'm writing this blog). There are several registrars out there who allow you to register domain names that contain Unicode characters. It's called International Domain Names (IDN) and IIS 7.0 and HTTP.SYS support it nicely. Here is what you do if you want to try it yourself: 1) Configure IE to use IDN server names for Intranet addresses You need a browser who converts IDNs into punycode . Name resolution systems like DNS don't work with Unicode and hostnames have to be converted to punycode first. Internet Explorer 7 does this automatically for Internet addresses. For our example you need to instruct IE to do the same for Intranet addresses. Go to "Tools" - "Internet Options" -...
IIS7 custom error module work in SendResponse stage with priority high (priority high in send response actually means lowest priority) which makes it one of the last modules to run in the pipeline. It produces custom errors only if current statusCode > 400. IIS7 custom error module produces four kinds of custom error responses. These are 1. Custom – This error is produced as per settings in the system.webServer/httpErrors section as seen for the requested URL. For information on how a merged view...( read more ) Read More...
One of the things which was not clear to me when IIS7 configuration system was written was how configuration system merges all the configuration data available and then decide what values are effective for the current request. One of confusions came from the fact that I assumed that IIS modules try to read the values for the current URL and then keep moving up till it finds the attribute explicitly defined in a configuration file. This is part true for the configuration system but never for the modules...( read more ) Read More...
There are four concepts that are important for you to understand to be able to effectively use the new Microsoft Web Deployment Tool. 1. Providers Providers are pieces of code that provide data to the tool for various operations like sync , migrate . The tool always starts with one provider, with an optional path for the provider. The provider builds the view of the part of the system it can handle, and uses other providers to represent system parts that they handle. These views are internally represented in xml. For example, if you begin with the dirPath provider, it will build an xml view of the folder (specified by the path), which will include files and subfolders present in it. It will delegate the task of handling files to the filePath provider and handling subdirectories to another dirPath provider object. Parameters you pass in the –source and –dest switches at the command line specify the providers which builds xml views of source and destination systems. Then, the tool only needs...
More Posts
Next page »