Complete Reference of my .NET Framework Builds

[yumeyao]

I'd like to compose a thread covering all technics used in my .NET Framework Builds.

I hope this reference helps people understand each cell and each action in my builds, and hope that people can update my addon when i'm not free, and hope that people who use an x64 OS can make an addon for x64 as good as mine x86 one.

Please note that Windows Installer Reference is a good helper and reading it should be a good habit for you in case you're encounter any syntax/structure questions on MSI.

The Windows Installer 4.5 SDK is available via direct link:
http://download.microsoft.com/download/ ... i45sdk.msi


I'll edit this thread gradually, and first I'd like to point 2 guidelines for addon makers who'd like to include my release and add language packs to it, making a localized addon:

1. Install 1.1 first, then 3.5, finally 4.0.

Maybe most people would follow the sequence of (4.0 3.5 1.1) or (3.5 1.1 4.0). These 2 sequences are good, they prevents File-In-Use issue when installing a .NET of higher version. But this reason doesn't act in my release because I have already updated all files in 1.1 and 3.5 to latest from 4.0.

2. Update some components in your language pack.
%LANG_ID% stands for Hex language ID for your language.
%LANG_STR% stands for abbreviation string of your language.

• .NET 1.1 LP:
  • Program Files\Internet Explorer\MUI\%LANG_ID%\mscorier.dll
    replace it with the one in my .NET release
    Program Files\Internet Explorer\MUI\1033\mscorier.dll
• .NET 2.0 LP:
  • Program Files\Internet Explorer\MUI\%LANG_ID%\mscorier.dll
    replace it with the one in my .NET release
    Program Files\Internet Explorer\MUI\1033\mscorier.dll
  • Win\System\MUI\\%LANG_ID%\mscorees.dll
    replace it with the one in .NET 4.0 LP
• .NET 3.0 LP:
  • Win\System\%LANG_STR%\UIAutomationCore.dll.mui
    replace it with the one in KB971513 for Vista, you can use this extracted one.
• .NET 3.5
  You should deploy KB982306 also to your language pack.
• .NET 4.0 LP: Same as .NET 3.0 LP
• BTW, XPS Printer's language pack is not needed and can be removed.

[yumeyao]

Basic Knowledge and Common Steps

Basic Knowledge:
Admin Deploy/Admin Install: msiexec /a msifile TARGERDIT="DIR"
do not really install an msi to your system, but to specified DIR, with all files extracted.


--- EDIT ---
.NET 4 Install Package Custom Build Tutorial with some basic knowledgeis completed:
I decide to make the tutorial this way: all steps are saved into HTMLs(webpages), so I can put images in wherever I want to place.

The forum posts will be filled with general information - that is to say, I'll explain everything behind each action deeply, but I won't tell you what to do in an exact step.

OK, the tutorial is done:
DNF40_Tutorial_With_UpdatedFiles.7z
It contains 2 webpages, I strongly recommend that you read GetStarted.htm first.

[yumeyao]

.NET Framework 1.1 Guide and Comprehension.

The guide is here(Sorry I don't have much time so this time it's in plain text and some images are provided):
http://www.filesonic.com/file/37056967/ ... torial.zip


Then I'd like to simple introduce why I do these.



3. Replace files with latest from Windows 2003 SP2.

This is because Windows 2003 SP2 provides files with higher version numbers than SP1.
Additionally, this benefits you installing this installer on Windows 2003 SP2.(*)

(*) In order to install this on Windows 2003 SP2, you should:
1. Remove the shipped-on .NET 1.1 component.
2. Completely disable WFP(Windows File Protection) or manually hack sfcfiles.dll. The Step4 actually benefits the latter, you'll have much less entries to do with sfcfiles.dll.



6.Remove extra routines added by a patch.

This series of action is a taken because these entries are either useless, or contained in each patch. For the latter case, you'll get these entries again if you admin deploy another post-SP1 patch, or if you are applying the patch to your system, these entries are automatically accounted by Windows Installer(the msi stays untouched though).



10.Repackage URTCoreCab.
This is done because .NET 1.1 will extract this cabinet first to initialize the actual installation(some other custom actions). Therefore repacking it won't make the files in-use are out-dated. Addtionally, I used the command line "cabarc -m none" to "save" them rather than "compress" them, so the files are not compressed. Then our 7z will take the advantage of solid compression to make the whole package even smaller.

[yumeyao]

There aren't too much points making .NET 2.0~3.5, most have been implemented in strel's Silent NET Maker Synthesized, including the most significant magic I have cast on, that is reduce 3.5's size and removing VC8/9 from them.

So I'd like to introduce how to integrate patches. I made a video because it's too complicated to explain each detail.
The video goes here: http://www.veoh.com/watch/v20926094xK8A5ZYw

This video, however, doesn't cover how my embedded vbscript is written. But it does show what the vbscript is for and how to add future updates' info into it. You can download my .NET releases and extract the vbscript yourself, and if you want, you can learn vbscript from any tutorial you can find, that's really an easy stuff.

[yumeyao]

For a complete tutorial on how my release is built, visit the tutorial: DNF40_Tutorial_With_UpdatedFiles.7z
It shows you the customization step-by-step. It contains 2 webpages, I strongly recommend that you read GetStarted.htm first.

Next I'll offer you an overview and explain why I do it this way, not other way.

Target:

• Slim Down the install routine(remove installer shell)
• Admin Deploy to remove x64 files on an x86-based OS
• Slight adjustment

Slim Down the install routine:

• The slimming down of the install routine benefits in several aspects, as I mentioned in [Tutorial]Modify an offline msi installer for administrative:
  1. You can deploy patches in the future, otherwise the msi package insists to copy unpatched files from its cabinet source.
  2. The size get compacted because unnecessary files are removed. (and x64 files are removed upon x86 package)
  3. The installation routine is simplified, one double-click on the msi is enough.

• So here are the principles
  • Remove all components that "decorates" the .NET Framework 4 body.
  • Keep all essential functionalities, such as uninstallation, receiving patches.

[5eraph]

Stickied.

[yumeyao]

Maybe the forum index is down due to last reply in this subforum?(I can't access this forum either)...
Try fixing it


--- edit --
well, not fixed...

[vmanda]

i can't acces too. just via search engine. Search "latest"

[yumeyao]

Tutorial for .NET 4 is completed, please check it out.
It's located at post #2(Basic Knowledge) and post #5(.NET 4).

The tutorial applies to both .NET 4 Client Profile and Extended.
The tutorial applies to both .NET 4 Redistribute Package and Language Package.

[yumeyao]

1.1 done.

2.0~3.5 will be done in the last, since strel's SNMSynth could generate a usable output while it handles 1.1 really poorly.



The adding patch in ARP for 2.0~3.5 and 4.0 will be introduced next.

[DirtyTodd]

Thats what I was looking for ...... Thanks for the great tutorial...

[DirtyTodd]

Please Reup this file....http://www.filesonic.com/file/37056967/ ... torial.zip

[spawn]

doe's the dot net cabs on http://www.mediafire.com/yumeyao# support xp x64?

[code65536]

Just a heads-up: Visual Studio 2010 SP1 and .NET 4 SP1 were released to MSDN a few hours ago. They'll probably make their way to the public download center within a week or two...

(And yes, this also means new v10 CRTs.)

[yumeyao]

Oh! The fastest sp1 ever. Do you still want to maintenance your runtime addon, since I have made one after you disappeared?

EDIT:

Just tried visiting dreamspark, not there yet.

[code65536]

Oh! The fastest sp1 ever. Do you still want to maintenance your runtime addon, since I have made one after you disappeared?

You should keep maintaining yours; you've done a good job with them.

[yumeyao]

http://go.microsoft.com/fwlink/?LinkId=208988
http://go.microsoft.com/fwlink/?LinkId=208989

found the links for vc 2010 runtime in vs2010 sp1 web installer package


EDIT:
Note: the runtime here contains both redist and debug dlls.

[jaynbe]

found the links for vc 2010 runtime in vs2010 sp1 web installer package

Yumeyao,

Thanks for these.

[ricktendo64]

http://go.microsoft.com/fwlink/?LinkId=208988
http://go.microsoft.com/fwlink/?LinkId=208989

found the links for vc 2010 runtime in vs2010 sp1 web installer package


EDIT:
Note: the runtime here contains both redist and debug dlls.

Any chance for the x64 version?

Edit: nm I got them by changing a few numbers of your x86 links

[yumeyao]

http://www.veoh.com/watch/v20926094xK8A5ZYw

The video tutorial for integrating updates into .NET Framework 2.0 and listing them in ARP is here.

[dumpydooby]

Great video. I watched the whole thing. I'm assuming I can carry over the practices in it to future iterations of the .NET Framework. Does that sound about right?


Also, lol @ the woman getting murdered at the 34-minute mark.

[bphlpt]

I also watched the whole thing. I'm just going to have to slow it way down when I try and do it myself. You are WAY faster than I am.

DD, you have very sharp ears, I had to go back and turn the volume up and listen closely to catch what you heard. LOL

Cheers and Regards

[yumeyao]

I live in college and that was the guys in neighbor buildings screaming.... They are very crazy on this. When I was 2nd-grade, they moved in. They I soon found the guys facing my window really annoying. LOL.

I suppose you guys are now able to do everything I can do on .NET, maybe there are still some points on .NET 2.0 ~ 3.5 that I do more than strel's script, but the amount is very limited and since I don't have much time to re-work 2.0 ~ 3.5 I can't figure out all of them. If you find any you can contribute here to let others know, of if you don't understand why I did something, feel free to ask here too.

[keloo05]

So, does this mean that you won't update you .NET addons anymore?

BTW, I wanted to watch the video, but...."Veoh is no longer available in ROMANIA. If you are not in ROMANIA or think you have received this message in error, please go to veoh.com and report the issue."

[yumeyao]

No. I will.

I can upload the video as a file to somewhere else later.

[bphlpt]

Until YumeYao has time to upload a copy himself, if he would like to, here's a copy of his Tutorial that I downloaded last night. The only thing I changed was the file name in order to add his name to it. This will be immediately removed upon YumeYao's request. It is totally his work, and this is the only place I will post this. This will remain here at his discretion. He can also copy this post, or any of the information in it, and repost it anywhere he likes. I will not delete the file from MediaFire unless he asks me to, so he is free to refer people to it for as long as he likes. If it gets deleted for some reason I will reupload it anywhere he asks me to.

File Name: YumeYaoTutorialIntegratepatchesintoNet.mp4
Time: 48:35
Dimensions: 1280 x 720
File size: 177,486,938 bytes
CRC32: 30938E4C
MD5: 979A56279625A93F9C780D4FF4AB54AB
SHA-1: 26F10D4943A81F2CE5F0AA8F203EE661BB1F687B
Link - http://www.mediafire.com/?p2op5v7muw1f54v

Cheers and Regards

[yumeyao]

Thanks bphlpt. I have a bad network connection now. I'll move to my company's dorm next month(hopefully) so I don't want to be busy changing the network now. Cheers.

[dumpydooby]

You're welcome to host this in that web space that I gave ya if you want.


Not sure if you were avoiding that because of the file size or something.

[ricktendo64]

yumeyao that trick you do in the command prompt where you only type 3-4 letters of the filename and its automatically entered, how do you do that?

[yumeyao]

@dumpydooby,
I avoid that concerning the traffic of your host .

@rick,
press 'Tab' key.

[keloo05]

No. I will.

I was confused. Thank you. I'm patiently waiting for it

[yumeyao]

Although I have locally updated the .NET 2.0/4.0/1.1 build but I have something else to do:

a new waitnet.exe for .NET 4.0
investigate into webclient issue which is reported in the Dutch subforum.


As talked, I'm busy at work so I don't have much time to complete these tasks. Sorry for the latency.

[ccl0]

i'm trying to remember something. i seem to vaguely recall something about microsoft making .net 4 intentionally slow down xp. but i can't for the life of me find that comment for reference. all i seem to remember is that (i think) it was discussed in yumeyao's posts somewhere

[bphlpt]

I'm sure whatever you remember was someone's opinion, rather than actual fact.

Cheers and Regards

[mooms]

.net 4 is not really needed in XP imo.

[shiner]

i'm trying to remember something. i seem to vaguely recall something about microsoft making .net 4 intentionally slow down xp. but i can't for the life of me find that comment for reference. all i seem to remember is that (i think) it was discussed in yumeyao's posts somewhere

I have it installed in my XP machine and don't notice any appreciable slowdown in my system.
I only installed it to try to learn how to use MSVS2010 Express to compile programs and dlls, for which NET4 seems required.

[ccl0]

i could be possible that i was thinking of something else. this was probably a year ago that i read -whatever- it was lol

[shiner]

i could be possible that i was thinking of something else. this was probably a year ago that i read -whatever- it was lol

No, your memory is correct because I remember an exchange of posts commenting on the topic of slowing down XP. It never concerned me until a few weeks ago, when I installed NET4 for the first time on my XP system to tryout MSVS2010 Express. Prior to that, I had only installed NET20. I used Rick's slimmed NET40 installer with the /ain switch and I haven't noticed any slowdown with my setup. My cpu is getting old and I think I would notice any significant slowdown due to installing NET40.

On the other hand, I do believe some XP Security Updates in the past 6-8 months have slowed my system down slightly. This is a subjective observation on my part.

[philorain]

filesonic has shutted its file sharing function. However, it is too late for me to find this topic, is there anybody who would like to distribute the tutorial?
BTW, the network environment is China, and you know the GFW
Here is my E-mail address, philo.rain@foxmail.com
Thx very much!

[EthanStark]

Project setup

The next step requires manually editing your .csproj file since Visual Studio doesn’t want to normally allow you to do this. This is how you can configure each build type to target a different framework version. You’ll first need to find these 2 entries:

<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
Inside each of these elements you need to explicitly tell these build configurations to use .Net framework 4.0 by adding this element:

<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
Next you’ll want to copy/paste both of these property groups and:

Change the Condition to check for the new build configurations and to target .Net framework 4.5
Change the OutputPath to have a specific .Net 4.5 folder
Change the TargetFrameworkVersion to be .Net 4.5
You should end up with 2 new elements that look something like:

<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug-Net45|AnyCPU'">
<DebugSymbols>true</DebugSymbols>
<OutputPath>bin\Debug-Net45\</OutputPath>
<DefineConstants>DEBUG;TRACE</DefineConstants>
<DebugType>full</DebugType>
<PlatformTarget>AnyCPU</PlatformTarget>
<ErrorReport>prompt</ErrorReport>
<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
<PlatformTarget>AnyCPU</PlatformTarget>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release-Net45|AnyCPU'">
<DebugType>pdbonly</DebugType>
<Optimize>true</Optimize>
<OutputPath>bin\Release-Net45\</OutputPath>
<DefineConstants>TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
<PlatformTarget>AnyCPU</PlatformTarget>
</PropertyGroup>
Next we need to do this for the MVC references or any framework specific references you need to target. In this example it is just the MVC references and you’ll need to wrap them with an ItemGroup element, you’ll end up with something like this to target the MVC 4 libs:

<ItemGroup Condition=" '$(Configuration)'=='Debug' Or '$(Configuration)'=='Release'">
<Reference Include="System.Web.Helpers, Version=2.0.0.0, .....">
<Private>True</Private>
<HintPath>
..\packages\Microsoft.AspNet.WebPages.2.0.30506.0\lib\net40\System.Web.Helpers.dll
</HintPath>
</Reference>
<Reference Include="System.Web.Mvc, Version=4.0.0.0, .....">
<Private>True</Private>
<HintPath>
..\packages\Microsoft.AspNet.Mvc.4.0.30506.0\lib\net40\System.Web.Mvc.dll
</HintPath>
</Reference>
<Reference Include="System.Web.Razor, Version=2.0.0.0, .....">
<Private>True</Private>
<HintPath>
..\packages\Microsoft.AspNet.Razor.2.0.30506.0\lib\net40\System.Web.Razor.dll
</HintPath>
</Reference>
<Reference Include="System.Web.WebPages, Version=2.0.0.0, .....">
<Private>True</Private>
<HintPath>
..\packages\Microsoft.AspNet.WebPages.2.0.30506.0\lib\net40\System.Web.WebPages.dll
</HintPath>
</Reference>
<Reference Include="System.Web.WebPages.Deployment, Version=2.0.0.0, .....">
<Private>True</Private>
<HintPath>
..\packages\Microsoft.AspNet.WebPages.2.0.30506.0\lib\net40\System.Web.WebPages.Deployment.dll
</HintPath>
</Reference>
<Reference Include="System.Web.WebPages.Razor, Version=2.0.0.0, .....">
<Private>True</Private>
<HintPath>
..\packages\Microsoft.AspNet.WebPages.2.0.30506.0\lib\net40\System.Web.WebPages.Razor.dll
</HintPath>
</Reference>
</ItemGroup>
Then we need to go ahead and copy/paste this block but target the different build configurations and then swap out these MVC 4 version references with the MVC 5 version references.