.NET Framework

@Tony
Can you please test this version..

@James,

    My Full Modified-Net Framework plugin is 100mb smaller installed than the v33test posted above and I was getting errors for missing files with .NET apps with v33test too that I'm not getting in mine.. (I am running v33test FULL 1709 & 1803 from CD, missing \4.0*\mscoreei.dll etc)

(Jumped into testing with @Tony to finally switch hoping it would be smaller than mine..)

Check my provide files to see what u need to grab for full and what u can erase, there is more that you can leave out than I did, there are some garbage folders FULL net needs so rarely they can be removed without worry, but I wasn't sure what else i could safely remove.. I think it was removal of the NativeImages folders that reduced it so much..?

Provided Files for Modified .NET v4(From Reply #91): https://mega.nz/#!lnBR3LjJ!gIYVtybITC5Nms0tafVpBqJJXyi2ODneg4iZExfujxY

**Updated, posted v3 by mistake at first..

The error has to be registry related...
As it is almost a FULL COPY OF ALL FILES..
Net is not really my bag,, and you seem to have a better handle on it..

Will test  later today (just saw this post). 

Builds taking 1.5 hours with cache activated; less time if NOT.   

@James,
attached is logfile and longer message.

Basically, DotNet.script v33T did not work for me. The 4 apps that I know need NET 4 or higher generate errors and do not run at all.

Running the Batfile that WORKS! for DotNet.script v31 DOES NOT work for v33.

Build ran longer because I forgot to turn off Windows Defender. I changed to "Run from CD", and selected the "2/3.0/3.5/4.5" selection as I usually do, for 1607.

PowerShell is the current version. Many other system plugins are older however.

After running the above as RunFromCD, this morning I tried again but RunFromRAM. The results are still the same: the 4 apps than need NET framework are not running. They give the identical error messages.  with RunFromRAM my boot.wim file went from approx 899MB to 1211 MB, so NET files are deposited on X: but are not working properly.

There is no \Microsoft.NET\ folder on Y:\Programs
but it is not on X: either. There are folders for Reference Assemblies, but no subfolders are labelled for 4.0, and no folder is named Frameworkx64 or Framework64. Odd.


Specific error messages are below
----------------------------------------------------------------------------------------------



Error at boot (when TrayStatus runs and needs NET 4).

---------------------------
TrayStatus.exe - Application Error
---------------------------
The exception unknown software exception (0xe0434352) occurred in the application at location 0x00007FFEB60C7788.
===================================================================================================================
---------------------------
ShowKeyPlus.exe - Application Error
---------------------------
The exception unknown software exception (0xe0434352) occurred in the application at location 0x00007FFEB60C7788.
===================================================================================================================
---------------------------
ILSpy.exe - Application Error
---------------------------
The exception unknown software exception (0xe0434352) occurred in the application at location 0x00007FFEB60C7788.
===================================================================================================================
---------------------------
Acrylic.exe - Application Error
---------------------------
The exception unknown software exception (0xe0434352) occurred in the application at location 0x00007FFEB60C7788.
==================================================================================================================

Same results with RunFromRAM as RunFromCD  DotNet.script v33T

If anyone else has the same "DotNetDetector doesn't 'light up the white letters and numbers' concern … 
That's what got me started on this quest. 
AND if you are using DotNet.script v31   
AND  you use LCID 1033 …  you can try just rewriting the registry.

What still works for me (Win10PESEx64 only, with Win10 1607 SourceDisksFiles) is
1) DotNet.script v31 plugin  for various NET 4 apps incl ILSpy that needs FW 4.6, with NET selection "2/3.0/3.5/4.5"
2) DotNetSupplement.script v1

I made the supplement from the 4 bob.omb registry files now converted with regCPE and placed in a separate plugin. This way it runs automatically during the build, instead of me running a BATfile manually after bootup. The main thing the supplement seems to do is let DotNetDetector look pretty; the LCID is hardcoded for 1033 en-US language-LOCALE, which is what I needed.



There is a cosmetic error because of regCPE inability to convert  QWORD lines in registry, but it seems to affect only a Date in 2 places. The v1 plugin has my explanation.

Posted because this frustrated me for a few years

What still works for me (Win10PESEx64 only, with Win10 1607 SourceDisksFiles)

What I am having an issue with is why are we providing files - when those files can be copied from install.wim
To get 3.0/3.5 you must enable Net3 other wise 4.* is copied by default

If selecting 2.0-4.5 Net the script copies the same files as FULL

The difference is that each version has different registry entries...
Script attachment>>>>>>>>>>>>>>

The difference is Version 4.7 is registry vs 4.6

I guess My point here was - that even though BOB is providing files..
The DOTNET script copied NET files when making your Core or Full selection....
As the NET file Versions went from 4.5 to 4.6 to 4.7 The same files where copied but those files are of the newer version...
But the registry is written with the OLD version Numbers...

THIS FULL COPY addition was never needed... The registry needed the be updated to the new version numbers...

By selecting FULL the registry version is 4.7 and a lot of additional files are copied
By selecting 4.0/4.5 the registry version is 4.6

BOB,
Please link me a copy of your COMPlete and Working Version of Net frame work..
SO I can come pare what you are copying and writing to the registry - to what the v30 dotnet.script is doing....

From reply #91 _ I am currently using this, warnings during build but irrelevant warnings as .NET installs perfectly..

Plugin (v4):  x64DotNet-Modified_Full_Provide_CDonly_v1803.7z (739.61 kB - downloaded 57 times.)

Provide Files: https://mega.nz/#!lnBR3LjJ!gIYVtybITC5Nms0tafVpBqJJXyi2ODneg4iZExfujxY

Thanks for looking at this I am hesitant because my strengths are in Win10x64 only

Please test the james version...
The only change to v30 script is different Version Numbers used In registry when selecting 1709/1803 Full

Looked at Tony's supplement and looked at Bob Modified scripts...

The common theme is the Registry...

As Bob uses provided files and tony uses 2.0/3.0/3.5/4.0/4.5 from current Dotnet script...
Both make changes to registry....

With Tony's additional reference to paint.net - which should be added to Paint.net Script

Not working run from CD FULL 1709 & 1803 - My mistake I think the paintnet is from my plugin.. 

BOB, Replace the Net detector with newer version

I would like us all to get on the same page and fix this thing....
I do not want to test with BOB's provide files - for now....
I want to figure out if it is registry related...

I can work around the hard coding of X and Y

As the script merges the current attachment of the X registry and then overwrites the X values with Y values when run from CD is selected, later on in the script....

or we hard code both X and Y values and then the script merge the proper registry..

That is what I TRIED to do in v31 - in addition to adding additional directories copied

Not sure we need all those additional directories or files - thus let's not test with provided files..

If its only registry you can use my plugin without provided files and see right away, just put 4 empty folders in the provide files section and see if the detector shows correctly

I prefer to not have to provide files as well

Why not:
If,%ScrollBox_RunFromWhere%,Equal,"Run from RAM",Begin
  Registry for Run From Ram
Else,
Registry for Run From CD/Normal
End


Nevermind sorry I asked its a nightmare inside that plugin 

Add your registry values to the James Plugin

I changed net detector

I can work around the script - need to know what works.....

Aren't the fusion files the fix? They are not in this version.. I am assuming I am supposed to be adding my keys to the Fusion_Y files.. Or do you want me to integrate my own way for runfromcd?

Aren't the fusion files the fix? They are not in this version.. I am assuming I am supposed to be adding my keys to the Fusion_Y files.. Or do you want me to integrate my own way for runfromcd?

Here I inserted the X - Y fusion reg

At this time the James testing script copies NO additional Files or directories...

I was about to post the results from DotNet Jamesv100 yesterday night, when I found the DotNet Jamesv200 plugin.

  ENABLED:  DotNet plugin JamesV200 from late yesterday    Selection: 2/3.0/3.5/4.5
 DISABLED:  DotNet plugin v31
 DISABLED:  DotNetSupplement plugin v1             

    burned:  6/11/18 WPEX264 on SANDGLID6, overwriting WPEX247 on USB3stick. 356. Remains as NTFS. Defender = OFF. 1 hr, 20 mins.
    tested:  WPEX264 on PAV17.
             TrayStatus (NET4), ShowKeyPlus (NET4), Acrylic Home (NET 4.5), ILSpy301(NET 4.6)             WORKS!
             but
             included DotNetVerDetector 18R1 only shows CLR 1,2,4 small white letters. Looks like NET 3, 3.5 might be missing
             but examining Y:\Programs\Microsoft.NET\  the subfolders are populated
             like Y:\Programs\Microsoft.NET\Framework64\v3.5
             and Y:\Programs\Microsoft.NET\Framework\v3.5           but no mention of 3.5.
             
             and does not show 4.6 except in the DotNetVerDetector text:
             
================ full text  of DotNetVerDetector ========================================
<32Bit>
2.0.50727.8745
  ->Y:\Programs\Microsoft.NET\Framework\v2.0.50727
4.6.1586.0
  ->Y:\Programs\Microsoft.NET\Framework\v4.0.30319

<64Bit>
2.0.50727.8745
  ->Y:\Programs\Microsoft.NET\Framework64\v2.0.50727
4.6.1586.0
  ->Y:\Programs\Microsoft.NET\Framework64\v4.0.30319

< Installed .NET Frameworks >

< Installed Updates >
Microsoft .NET Framework 4 Client Profile
 KB2468871
 KB2468871v2
 KB2478063
 KB2533523
 KB2544514
 KB2600211
 KB2600217
Microsoft .NET Framework 4 Extended
 KB2468871
 KB2468871v2
 KB2478063
 KB2533523
 KB2544514
 KB2600211
 KB2600217
 KB2468871
 KB2468871v2
 KB2478063
 KB2533523
 KB2544514
 KB2600211
 KB2600217

< Installed Languages 3.0>
< Installed Languages 3.5.x>
< Installed Languages 4.x>
==========================================================================================

The registry keys for NET 2,3,0, 3.5 are missing, including the Values like Release
that DotNetVerDetector seems to use for its large white numbers display.

Plugin: DotNet v200 on Win10PESEx64, SourceDiskFiles: Windows 10 Pro x64  [10.0.14393.0]   1607
Selection:  2/3.0/3.5/4.5    not the FULLest