Great!

Web Deployment projects can be used with either the "ASP.NET Web Site" or "ASP.NET Web Application Project" options built-into VS 2008, and provide a few additional build, packaging and deployment options for you to use. You can read an old tutorial post of mine here to learn more about they work.

The VS 2008 Web Deployment Project version supports all of the existing features provided by the VS 2005 web deployment download. It also adds additional support for:

Easily migrating VS 2005 Web Deployment Projects to VS 2008 Web Deployment Projects
Replacing output only if web deployment builds succeed
IIS7 Support
This RTW (release to web) version fixes bugs and adds some small features that people requested in the December CTP version they released last month. Please make sure to run setup and uninstall any older version of the VS 2008 Web Deployment Project support you have installed before installing this final version. VS 2008 Web Deployment Projects can be installed side-by-side with VS 2005 Web Deployment Projects - so there is no need to uninstall the VS 2005 version if you are still using it with older projects.

More Deployment Features

This tool works with both IIS6 and IIS7 and enables automated copy deployment, file synchronization, and migrating of applications onto web servers. If you are looking for a great way to automate the deployment of your ASP.NET applications onto remote servers then this tool is definitely one to check out.

Download

You can use VS 2008 Web Deployment Projects as a post-build step within your build environment to fix up last minute deployment settings - and then use the IIS Web Deployment tool to copy them remotely onto server machines. Alternatively you can also use the IIS Web Deployment Tool to copy vanilla "ASP.NET Web Site" or "ASP.NET Web Application" projects to remote machines (no VS 2008 Web Deployment Project required).

To learn more about the new IIS Web Deployment tool, read the walkthroughs at the bottom of this page (in particular the "Introduction to MS Deploy" one). I will also be doing a blog post in the future that talks more about how to use it to automate your web server deployments.

Walkthrough

thanks Scott

The last 2 days I’ve been able to follow an OPEN XML course given by Wouter Van Vugt...

And i must admit that I’ve seriously underestimated the power of openXML in office 2007...

In the past I have been playing with the sdk and com's to create office documents but these always ended up in complete disaster...

But now I’m sure that after a few weeks playing with the packages and all those XML tags, this won't be any problem anymore..

Here's a list of the items that are very interesting to play with:

Wouter Van Vugt blog

Package Explorer Tool

enjoy!

Attached is a downloadable copy of "Open XML Explained" by Wouter Van Vugt, the first book on Open XML development. The sample documents for the book are also available for download here.




This 128-page book covers the basics of Open XML, including many of the topics covered in the Open XML developer workshops, as well as several additional topics. The author, Wouter Van Vugt, is a software development trainer/consultant who specializes in the Open XML file formats. You may know from his participation in the forums here on OpenXMLDeveloper.org, or from his blog where he covers Open XML and other .NET development topics.

Download E-Book

At this moment i'm at infosupport to learn more about openXMl, it seems very interesting.. I hope i can tell you more about in the near future

Add the connectionstring to the Machine.Config

public static void SaveToMachineConfig(ConnectionStringSettings connection) {
Configuration configurationmanager = System.Configuration.ConfigurationManager.OpenMachineConfiguration();
configurationmanager.ConnectionStrings.ConnectionStrings.Add(connection);
configurationmanager.Save();
}

Retrieve the connectionstring from the Machine.Config

private static PermissionDataContext m_persmissions;
internal static PermissionDataContext PermissionsDb
{
get
{
if (m_persmissions == null)
{
string Currentconnecionstring = ConfigurationManager.ConnectionStrings["NameOfThe ConnectionString"].ToString();
m_persmissions = new PermissionDataContext(Currentconnecionstring);
}
return m_persmissions;
}
}

Location where Machine.config is saved:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config