The Microsoft Build Engine (MSBuild) is the new build platform for Microsoft and Visual Studio and included in the .NET Framework 2.0.
Additionally to the built-in tasks I found the following:
- MSBee: Compile assemblies targeting .NET Fx 1.1 (MSBuild extension)
MSBuild Extras – Toolkit for .NET 1.1 “MSBee” is an addition to MSBuild that allows developers to build managed applications in Visual Studio 2005 that target .NET 1.1.
- Update Assembly Version Numbers (Task)
The AssemblyInfo task provides a way to manipulate the content of AssemblyInfo files at build time. It works with C#, VB, and J# AssemblyInfo files. The primary use of the AssemblyInfo task is to set assembly version numbers at build time.
This post will be constantly updated as new extensions are available.
Your Feedback requested!
Do you know more exciting MSBuild tasks and tips? Drop me a comment!
After installing .NET Framework 2.0, No-Touch Deployment apps (HREF-EXEs) are broken. When you try to navigate to the EXE via a URL it prompts the user to Run or Save the EXE instead of launching it with IEExec.
See the bug details on MSDN Product Feedback Center
Update #2:
Microsoft finally released a KB article about this topic here.
Update:
Microsoft decided not to support HREF Exes from the Internet Zone in the .NET Framework 2.0.
It is known that this is disruptive to people that were using the feature, and there are several approaches to working around this limitation as described in the "Workarounds" section of this page.
- Add site to Intranet Zone or Trusted Sites Zone
Workaround Description:
Add the site being used to the Intranet Zone or Trusted Sites Zone.
The restriction on HREF Exe usage only affects the Internet Zone.
Workaround Steps:
If you are not familiar with adding sites to zones follow this instructions.
- Use browser controls
Workaround Description:
Use browser controls to run the same code. There is support for OBJECT tag browser controls which will run in IE against .NET Framework 2.0. You can load the original HREF Exe application via the browser control, although it will not run in a separate process any more.
Workaround Steps:
If you are not familiar with .NET browser controls hosted by Internet Explorer see this MSDN Mag article and this this KB HOWTO.
- Migrate to ClickOnce applications
Workaround Description:
Ideally, migrate to ClickOnce applications (it is absolutely understood that this is not a simple request, but ClickOnce applications are the preferred way for launching code through the browser).
Workaround Steps:
To find out more about ClickOnce in the .NET Framework 2.0 refer to this website.
- Configure Registry Key to allow HREF EXEs from the Intranet Zone (not recommended)
Workaround Description:
Configure the following registry setting on the client machines:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
"EnableInternetHREFexes"=dword:00000001
Workaround Steps:
Create the registry value as stated in the description on all client machines.