If .NET EXEs is targeting .NET 2.0, the problem can be resolved if before
shelling the .NET exe, developers can use XML Serializer Generator Tool
(Sgen.exe
Follow the following series of steps:
1. Assuming that the unshelled exe is TestKey.exe, run sgen
2. Now Shell the exe and copy paste the .XMLSerializers.dll generated in
3. Running the Shelled exe now should execute it fine.
Question 8 - Why do vista applications that require .mui files fail to
run when protected using Quick Shell and Shell methods?
These protected files on vista need .mui
stored inside the default language folder (for example, en-US for an English
version) that must be placed at a location where the protected executable
resides.
For example, for an English version of vista, if the protected Notepad.exe
resides in C:\ protected then the .mui files must reside at the same location
inside the en-US folder. Please check for the .mui files, located at the location
as advised in the example.
For more FAQs, refer to the Sentinel Keys Toolkit Help.
Question 9 -Are there any special files to be distributed to the end
user for applications protected using the .NET enhancement
feature?
The following DLLs should be distributed to end users:
■
1.The sgen.exe utility can be found in "Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin"
folder of Visual Studio Installation.
2.Files required for language and region settings.
Sentinel Hardware Keys Developer's Guide
1
) to create an XML serialization assembly for types in the .NET exe.
TestKey.exe in command prompt.
This creates TestKey.XmlSerializers.dll in the same folder.
step 1 to the same folder where the shelled exe is located.
For 32-bit .NET applications protected using Enhanced .NET Security
option:
Frequently Asked Questions
2
files to execute. These .mui files are
87
Need help?
Do you have a question about the Sentinel and is the answer not in the manual?