Jump to content











Photo
- - - - -

.NET Framework Full (1.0, 1.1, 2.0, 3.0, 3.5, 4.0) Script for LiveXP


  • Please log in to reply
28 replies to this topic

#1 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 25 March 2011 - 08:12 PM

.NET Framework Full: 1.0, 1.1, 2.0, 3.0, 3.5, 4.0
*****************************************************

LiveXP WinBuilder Script for .Net Framework support

How to use it:

1. Extract both files (dotNetAll_henshaw.Script and
dotNetAll_henshaw.7z) into the same projects subfolder.
Do not rename them unless you know what you're doing.

2. Select the script ".Net Framework Full" from WinBuilder.

3. Run your net applications in LiveXP by calling them like this:

cmd.exe /c "path\yourApp.exe"

Here is an example:

In this example, we will create a desktop link to run a dotNet application.
Let's say you have a script for your dotnet application MyApp.exe in
your build. You want to install MyApp.exe to

"Program Files\My Application"

So, let's make a desktop shortcut to run this application:

//===========================

[variables]
%ProgramTitle%=My Application v1.0
%ProgramEXE%=MyApp.exe
%ProgramFolder%=My Application
%cmd%= #$pSystemRoot#$p\System32\cmd.exe
%path%=%Target_Prog%\%ProgramFolder%\%ProgramEXE%
%param%=/c#$s#$q%path%#$q

[process]
Add_Shortcut,Desktop,,%cmd%,,,%param%,%path%

//===========================

Actually, we are running the thinstalled cmd.exe and passing /c as the
first parameter and your application "MyApp.exe" as the second parameter.

Start-up time for dotNet applications will be a bit longer than normal
because I did not include the IL-NativeImages for space reasons.
These precompiled IL-libraries speed-up the live-compilation process of
net application thus reducing start-up time, but will increase the package
size to about three times.

More to that, to make a reasonable size, I had to apply some compression.

Attention:
Some applications like nlite, will report missing libraries-error then quit.
This is because, such applications call some other applications which fail
to see the virtual dotNet file-system because not loaded with the "/c"
parameter.

However, there is a work-around that. I will implement that in subsequent
revisions of my scripts.

Test your apps and give feed-backs.

Henshaw.

Download: .NET Framework Full (1.0, 1.1, 2.0, 3.0, 3.5, 4.0)


25-Mar-2011



#2 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 25 March 2011 - 09:30 PM

Upload was corrupted. Now re-uploading...

Back soon!

#3 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 25 March 2011 - 11:57 PM

Get it from here!!!

Download (updated link):

.NET Framework Full (1.0, 1.1, 2.0, 3.0, 3.5, 4.0)



#4 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 26 March 2011 - 02:20 AM

I just tested 10 dotNet applications on LiveXP. 5 of them ran smoothly, the others generated a Protected Memory Read/Write error.

These should be caused by an inadequate level of virtual registry isolation of certain reg keys.

I will try to solve it this weekend.

Good Night!

#5 i

i

    Silver Member

  • Advanced user
  • 522 posts
  •  
    United Nations

Posted 26 March 2011 - 06:25 AM

:cheers: 4 posts by same user (from WonkoLand) did not edit instead of posting news...




@Henshaw thanks anyways... :cheers:







Can anyone answer a stupid question, this maybe for LiveXP however, on standard XP install, if I choose to install 4.0, do i need to install other versions? 1.1? 2.0? 3.x? Logic tells me obviously "NO" but, standalone installer size of each version (in progressing order) is very strange... :merc: Also, i generally avoid apps that use dot net stuff...


dotNetFx40_Full_x86_x64.exe 48.1MB (what happened here? higher compression?) (x86 & x64)


.NET Framework 3.5 Service Pack 1 (Full Package) 231.5MB

.NET Framework 3.5 197.2MB

.NET Framework 3.0 50.4MB (x86 only)

#6 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 26 March 2011 - 10:42 AM

:cheers: 4 posts by same user (from WonkoLand) did not edit instead of posting news...




@Henshaw thanks anyways... :cheers:







Can anyone answer a stupid question, this maybe for LiveXP however, on standard XP install, if I choose to install 4.0, do i need to install other versions? 1.1? 2.0? 3.x? Logic tells me obviously "NO" but, standalone installer size of each version (in progressing order) is very strange... :merc: Also, i generally avoid apps that use dot net stuff...


dotNetFx40_Full_x86_x64.exe 48.1MB (what happened here? higher compression?) (x86 & x64)


.NET Framework 3.5 Service Pack 1 (Full Package) 231.5MB

.NET Framework 3.5 197.2MB

.NET Framework 3.0 50.4MB (x86 only)

Every dotNet application needs only one specific framework: the one from whose arhitecture it was developed. An application that needs netFx4 does not need any of the others to run and vice versa. The problem is that Microsoft is doing nothing to make new dotNet frameworks backward compatible.

Since every developer is free to chose which framework to work on, it is advisable for those who use a variety of dotNet applications to have all frameworks installed.

Setup packages of dotNet frameworks may deceive you because, at install time the packages grow to about five or seven times. This is not due to heavy compression on the packages. To understand what happens, you need to know roughly what is dotNet and how it functions. It is a very big discussion, but I'll hereby give you a few hints:

1. dotNet Framework is a tecnology that was born to solve application-hardware compatibility issues. In this way dotNet applications do not see your hardware but the net framework. Therefore, dotNetFx is simply a hardware emulation level. Software developers will therefore, no longer bother about hardware issues and users also.

2. To accomplish this, many system libraries are generated by compilation at framework install-time for each predetermined hardware type, producing a very large bunch of almost similar files which in turn will be selectivly compiled on-the-fly at application runtime to produce the specific needed machine code for execution.

3. More to that, by default, all framework setup packages are deflated and backed-up within the install directories to permit rapid automatic repairs.


So as you see, there is no magic behind it. After installing all dotNet Frameworks from 1.0 to 4.0, you will have disk space-cost of about 2.3 gigabytes. If you know what to take off, what to leave, and the relative consequences, you might bring down the disk-cost to about 500 megabytes. With good file arrangement and useful compression, you may endup with roughly 200 megs.

dotNet 3.5 setup is large because it contains netFx 2.0, 2.0 SP2, 3.0, 3.0 SP1 and 3.5 itself. As I said, no magic!

hope that helps!

Edited by Henshaw, 26 March 2011 - 10:58 AM.


#7 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 28 March 2011 - 11:48 AM

Based on problems found in my dotNet loader scripts, I am building another version for dotNet Full. Please, refer to this link for more insights:

http://reboot.pro/14...post__p__125822

#8 MrChucong™

MrChucong™

    Member

  • Members
  • 59 posts
  • Location:Small City
  • Interests:Life Or Death
  •  
    Vietnam

Posted 18 September 2011 - 07:47 AM

thank for shared

#9 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 11 March 2012 - 10:11 PM

Coming up soon:
In a couple of weeks from now, I will start woking again on .Net Framework Full that will now include also dotNetFx4.5 (from 1.1 to 4.5 in a comprehensive package). I will try to make it as slim as possible and compatible to all live systems (from LiveXP up to Win8PE).

So, if you have any nice dotNet dream for Windows Live, it's time to make a suggestion.

Stay tuned!
  • kjr0912 likes this

#10 mastermindpro

mastermindpro

    Newbie

  • Members
  • 11 posts
  •  
    United States

Posted 05 June 2012 - 03:36 AM

Henshaw, did you get anywhere with this? I'm trying to get .Net 4 added to my image and finally succeeded, but it's huge (my WinPE_SE build went from ~400MB compressed to 850MB compressed). If you are close to being done with your version, then I'll hold off.

#11 rogierios

rogierios
  • Members
  • 7 posts
  •  
    Belgium

Posted 04 July 2012 - 07:45 PM

Can anyone upload this script (both links are dead) and can anyone confirm if this works?

Or, if someone knows another post that contain a good .NET Framework script (or even bartpe) ?

Thanks! :clap:

#12 kjr0912

kjr0912
  • Members
  • 1 posts
  •  
    South Korea

Posted 07 January 2013 - 10:49 AM

link plz....

i want .net 4 script



#13 ohlala

ohlala
  • Members
  • 8 posts
  •  
    Vietnam

Posted 24 January 2013 - 01:53 PM

I can't download, link die, how can share?

 

Thank



#14 Joyou Leung

Joyou Leung
  • Members
  • 4 posts
  •  
    Hong Kong

Posted 06 November 2013 - 04:57 AM

Download link failure, give the new download link. Thank you



#15 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 06 November 2013 - 10:22 AM

I have been too busy with my job and family that I had to drop so many hobby projects.

I hope to get some bit of time in future.

 

Please, give a day or two. I will get it from my archive, upload somewhere, then

update the links.



#16 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13329 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 06 November 2013 - 10:43 AM

Please, give a day or two. I will get it from my archive, upload somewhere, then

update the links.

Henshaw, if you cannot access the board "Files" section for uploading, ask Nuno, he will provide you with permission to upload the file to the board, so that it will (hopefully) be "permanent".

 

:cheers:

Wonko



#17 Joyou Leung

Joyou Leung
  • Members
  • 4 posts
  •  
    Hong Kong

Posted 06 November 2013 - 11:05 AM

I have been too busy with my job and family that I had to drop so many hobby projects.

I hope to get some bit of time in future.

 

Please, give a day or two. I will get it from my archive, upload somewhere, then

update the links.

I wish you a happy life and thank you for uploading will be updated after the link. Thank you



#18 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 09 November 2013 - 11:57 AM

Here's the updated link:

 

http://hoat.biz/down...w_2011-03-25.7z

 

I will now be hosting this file on my website. In the next few days I will update all other links I have posted.

 

This script uses the Thinstall style, which I later thought was less efficient. With the dotNetFx2 project I switched to the

dotNetRunner style which proved to be better. So, I then planned to update this one also but lacked the time.

 

OK, this coming week, I will switch this project to the dotNetRunner style.

 

How I do the dotNetRunner style?

 

I put all essential net framework files in their respective places at build time, then dotNetRunner.exe

patches the LiveXP registry at boot time. It is just a registry patch, not a service. This is because WinBuilder cannot do it at build time.



#19 Joyou Leung

Joyou Leung
  • Members
  • 4 posts
  •  
    Hong Kong

Posted 12 November 2013 - 05:53 AM

This script can be used in Win7PE SE? ?



#20 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 12 November 2013 - 10:43 AM

Yes!

 

This script was made for LiveXP as the basic system. However,

.Net Framework is a subsystem on its own. Its just like a virtual machine running another

operating system. In this case, dotNet is our virtual operating system running in our dotNetFX

virtual machine, which will be responsible for running our dotNet applications.

 

Thus, dotNetFX has little to do with the host operating system. 

I made it for LiveXP but should be compatible with all Windows NT operating systems and their

Live versions from XP and above (WinXP, LiveXP, Windows Vista, VistaPE, Windows 7, Win7PE,

Windows 8, Win8PE, etc.)

 

To use it as a Live dotNetFX on a normal windows operating system, extract it from the script

using the tools found in this forum then run your applications with the parameters stated in

the script instructions.



#21 Joyou Leung

Joyou Leung
  • Members
  • 4 posts
  •  
    Hong Kong

Posted 12 November 2013 - 12:29 PM

How to add a script to Win7PE SE inside to be effective.Thanks!



#22 Henshaw

Henshaw

    Member

  • Advanced user
  • 68 posts
  •  
    Italy

Posted 16 November 2013 - 04:22 PM

If you mean adding a script for a dotNet application into your Win7PE SE build, just do it as you would do

for any other WinBuilder script, i.e. extract your desired script(s) into a sub-folder of your build in the

projects directory.

 

.NetFramework is a virtual machine but does not host applications. It simply recieves and processes dotNet

system calls. Your dotNet applications should be installed into any directory of your choice.

 

I doubt if I understood your question...



#23 t6nna

t6nna

    Newbie

  • Members
  • 13 posts
  •  
    Estonia

Posted 01 September 2015 - 02:34 PM

Is there any place from where I can download it? All download links are dead...



#24 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12686 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 01 September 2015 - 02:48 PM

The links are 4 years old. public storage servers sometimes store only for shorter time.

 

I suggest to PM the author of the script and ask for personal sending.

 

Peter



#25 t6nna

t6nna

    Newbie

  • Members
  • 13 posts
  •  
    Estonia

Posted 01 September 2015 - 04:24 PM

Thnx, I would try that.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users