|
Version 4.0.4650
- Added new options to the Item / Settings dialog. Read more...
- Improved Save for Integration processing.
- Cleaned up help.
- Fixed minor bugs (truncated messages, wrong value saved in
project, formatting, etc.)
Version 4.0
- Visual Studio 2010 integration is now available. Read more...
- New command line build options. Read more...
- New item settings dialog. Read more...
- Application and DLL manifests can now be embedded automatically.
- Added elevated self-registration for COM DLLs - needed with VS2010 sp1.
- Fixed minor bugs.
- Updated help.
- Free upgrade from version 2 and 3 - use the same license file.
Patch for version 4434: Error 0x80070005: Access is denied.
You may experience error "Access denied" when building manifests for COM
DLLs created using Visual Studio 2010 sp1. Read more..
Version 3.7.4434
- "Embed CLR manifests" switch in sxs32cmd.exe did not work as expected, fixed.
- Shared assembly dialog took a very long time to initialize on Windows 7, fixed.
Note: build 3.7.4433 has been superseded.
Manifest Maker MSBuild task is available for testing
We are working on full integration of Manifest Maker build into Visual
Studio 2010. In the meantime we wanted you to have a chance to try the coming
MSBuild task which is independent of Visual Studio and will be included
in future releases of Manifest Maker in addition to VS2010-specific tasks.
see more on the download page...
Version 3.7.4357
- Added new handling of multiple type libraries in a DLL.
Read more...
- Added embedded manifest number command line switch.
Read more...
- Fixed CLR meta data errors.
- 'Use current registration' paths not recognized, fixed.
- Fixed minor bugs.
- Updated help.
Version 3.6.4325
- Fixed bad namespace in the <windowsSettings> tag.
- Improved setup to detect when a newer version is already installed.
- Updated help.
Version 3.6
- Manifest Maker now supports "dpiAware" and "supportedOS" attributes
in application manifests.
- Bugs fixed:
- Auto-fix failed on German Windows 7
- TLB export hung when TLBEXP.exe generated large number of messages
- Cosmetic changes
Version 3.5.587
- Manifest Maker can now include 'runtimeVersion' in <clrClass> elements.
Version 3.5
- Manifest Maker is now supported on Windows 7 and 2008 Server R2.
- CLRClass manifests can now be automatically embedded in CLR DLLs.
Check online help for more information.
2008 Server R2 side-by-side hotfix is available
Knowledge base
article KB977787
discussing the IIS 7.5 (2008 Server R2 and Windows7) side-by-side problem
is available on the Microsoft support site.
The corresponding hotfix can now be
downloaded here. Click Show hotfixes for all platforms and languages
to see all available versions.
2008 Server R2 and Windows 7 break side-by-side in IIS
Both Windows 2008 R2 and Windows 7 include a new version of w3wp.exe
- the IIS application pool host process - which has an embedded manifest.
The embedded manifest is loaded as the process default manifest and the
recommended web application isolation
method no longer works.
Version 3.4
- Manifest Maker is now using a new, simplified, licensing model.
Read pricing structure here.
- Manifest Maker can now generate assembly references using generic
'processorArchitecture'. Check online
help for more information.
- Added corresponding options to the Manifest Maker command line build
tool. Check online help for more
information.
Version 3.3.545
- Manifest Maker can now compress shared assemblies into MSI files.
Check online help for more information.
- Added new options to the Manifest Maker command line build tool.
Check online help for more information.
- Resource manifest viewer can now reformat the manifest XML to make
it more readable.
- Shared assembly names can now use non-ANSI characters.
Version 3.3
- Added new build options to Manifest Maker. Check
online help for more information.
- Added new options to the Manifest Maker command line build tool.
Check online help for more information.
- Changed Visual Studio Integration start menu icons. Added new icons
for adding and removing Manifest Maker path to/from Visual Studio VC++
project properties. Check online help
for more information.
- Known issues:
- Signing shared side-by-side assemblies fails if the assembly file
path (folder or file name) contains non-ASCII characters. We are working
on a fix.
Windows Server 2003 SP1 side-by-side performance problem: hotfix is
now available
The slow side-by-side response on 2003 Server sp1 has now been addressed
by Microsoft. Details are at
http://support.microsoft.com/kb/953876.
Version 3.1
- Manifest Maker did not work on some non-English versions of Windows
Vista - fixed.
- Manifest Maker now searches for tools in the path and only if a
tool is not found, in other locations.
- A memory leak on Windows Vista is fixed.
New information on isolating ASP .Net 2.0 web applications
ASP .Net 1.1 included support for using Windows win32 side-by-side (registration-free
COM) to access COM objects without having to register them on the server.
ASP .Net 2.0 dropped that support. Updated examples are now included with
the latest Manifest Maker download. Read the
online help on how to isolate ASP .Net 2.0 applications.
Version 3.0
Vista-compatible Side-by-Side Manifest Maker 3.0 is available for
download. What is new:
- Changed UI. The main window is now a resizable splitter. As previously
the main project is in the top list and the build dependencies are in
the bottom list.
- Manifest Maker now recognizes embedded resource manifests. During
build DLLs with embedded manifests are treated as assemblies. No manifests
are built for them but, instead, the embedded manifests are referenced.
- New utility for viewing embedded manifests.
- Refined rules for using files in various build types.
- Version 3.0 uses
the same license files as version 2.
- Vista users: due to the implementation of side-by-side
features in Windows Vista, Manifest Maker must run "as administrator".
The embedded manifest contains appropriate information so you will be
asked to allow administrative access upon program startup.
- Vista users: Manifest Maker integrated into Visual
Studio also needs administrative access. If you run Visual Studio as
limited user you will be prompted each time Manifest Maker runs during
your build. We suggest you run Visual Studio "as administrator" to avoid
this prompt.
- Vista users: Auto-fix will not work in Windows
Vista unless you install hotfix
KB935200.
Vista hotfix for RegisterTypeLib() API is available
Side-by-side with ASP .Net 1.1 on 2003 Server SP2 is now fixed
- In ASP .Net 1.1 you can take advantage of win32 side-by-side by
simply dropping a "web.manifest" file in the application directory
(see details).
- This was broken in 2003 Server service pack 2. A hotfix is now available:
http://support.microsoft.com/kb/939044
Service Pack 2 for Windows 2003 Server and Side-by-Side in ASP .Net
1.1
- In ASP .Net 1.1 you could take advantage of win32 side-by-side by
simply dropping a "web.manifest" file in the application directory
(see details).
- Apparently as of Windows 2003 Service Pack 2 this is no longer the
case. It appears that this functionality has been removed. Stay tuned
for further developments. In the meantime you may need to use the HTTP
module approach or simply add explicit activation context management
to your application.
Click here for more history...
Note
Support for all builds of version 2 of Manifest Maker has been phased
out as of April 30, 2010. Please upgrade to version 3. The upgrade is free.
Use the same license file.
|
|