DOTNET program rushed to Window XP, experience the beautiful appearance?
Small gas god 2001-09-16
My friend has finally can't help but start to install Windows XP, and I feel that it is tempting that is gorgeous interface. It seems that the version of a Windows XP 2600 that has been circulated online is very stable and does not activate (so the installed person gradually has more haha). Because I have to help him install some peripherals, I can do such an experiment, start thinking about migrating some of the DOTNET programs to XP, especially some WinForm procedures, because I think my own procedure can also use XP Gorgeous UI.
There are a lot of sayings about XP, some have pre-installed DOTNET FRAMEWORK BETA2, and some say that there is no installation, I think this is mainly the DOTNET running library. There is no release must consider, from Beta1 to Beta2 changes. This must be directly affected by the stability of the operating system. (This can also be smashed with the delusions between WinXP and DOTNET. They always think that one of XP is written in DOTNET). In fact, this retail version in my hand also doesn't have Framework beta2 runtime, When I passed the program directly COPY, I can't run. As for this running library, there are two ways to solve (of course, there should be countless methods):
1. There is a setup.exe execution file in the DotNetFramework directory in the CD of the component update of your Visual Studio.Net Beta2, which is executed under XP, and then perform your DotNet program.
2. Large or complex programs, you can use the VS.NET's setup and deployment feature to make a setup program to complete this work. Specific you can:
1. Open the DOTNET program you want to deploy.
2. File-> New-Project ... in the open New Project dialog
3. On the left selection setup and deployment project Right to the right column Selection Setup Wizard Note the following path and options, select the addition to the current project, not close.
4. Then there will be a Wizard appears from 1 to 5 to the new Project to automatically join your SLN. (If you don't choose Setup Wizard, you can click Project in the SLN Explorer View on the right side of VS.NET and then select Add Project Output in the tree view. And Localized Resource, two indicates that you need to pack your run files and some resource files)
5. OK recompiles all your Project You can find an MSI file in your setup project's debug or release output directory. It is possible to install it in XP.
Honestly, the second method is broken, and the running library files of almost the entire DOTNET are extracted, so the size is very large, generally more than 15m. Of course, you can also install Framework Beta2 SDK or VS.NET to make XP with DOTNET running libraries.
After that, I started some interesting experiments and put my WinForm program to XP. A few days ago I saw someone in the 9CBS to tell how to adapt to XP in the VC environment. I think DOTNET is also possible, or even VB procedures can also be. The total feeling is OK, almost very smooth. I would like to thank www.godotnet.com. Because I was done by referring to this article. http://www.gotdotnet.com/team/windowsForms/themes.aspx
There are specific steps and some instructions above, I said some specific steps:
1. Set the values of all the controls with the flatstyle attribute in your WinForm to System, no more even.
2. Compile your program into an EXE file
3. If you have a DOTNET running library, your exe program goes to XP.
4. Prepare a manifest file that is the same as you run with your EXE file, there is almost the same, the content is almost the same, mainly its file name must be "your running program name .manifest", such as I The program is Win2kToxp.exe, then this file must be named: win2ktoxp.exe.manifest (there is a sample on this manifest file website, and I came with one I tested to everyone, I like the one directly has a problem.)
5. This article also introduces a way you can directly embed this manifest, I also tested OK. (You can generate EXE to do this step, the type introduced when modified is: RT_Manifest, then change the resource type from 101 to 1, save you. I feel this is a good design, when you decide yourself The program is going to run in XP and then do this, but the premise must ensure that you are successful in the fourth step, otherwise it will cause the entire program to be run after the process is modified.
In short, this is a very interesting experience. If you have the same environment, you can try it.
I completed my DOTNET program and compiled into EXE in Windows 2000 ADV Server SP2 EN, VS.NET SP2 En. Make sure the XP has a run library to go to the XP environment execution.
Here is the copy map of the screen:
Below is a list of manifest:
Version = "1.0.0.0" Processrarchitecture = "x86" Name = "Win2kToxp.exe" TYPE = "Win32" /> TYPE = "Win32" Name = "Microsoft.Windows.common-controls" Version = "6.0.0.0" Language = "*" ProcessRarchitecture = "*" PublickeyToken = "6595b64144ccf1df" /> especially: The above text involves other people's privacy and personal rights, such as non-authorized or agreed by me, please do not publish, reprint, repost, or other forms of communication anywhere or journal. All of the above text or pictures are only used for internal communication, not any news published and commercial purposes.
