![:cheers:](http://reboot.pro/public/style_emoticons/default/cheers.gif)
I was wondering would there be any mileage in trying to make Dotnet framework portable? Many hate Dotnet framework, it goes without saying but whether we hate it or not it is part of the software scenery!
Questions arise?
Dotnet framework like the programs that are propelled by it has undertaken various stages of evolution & has been incorporated within successive editions of M$ servive packs so the question at what point of entry do you enter the portable world. Having said that some people have not necessarily installed any further service packs albeit, my guess-ter-mit would be that they would be few and far between. However this would be a factor especially when file-sets & registry entries would need recording. I wonder also whether the internal structure of existing files are altered in the updating process?
Would be interested in feedback on this as so many programs are geared towards to Dotnet Framework these days so if dot net could be recorded in the installation process it could possibly be a candidate for portability.
I have briefly searched the net and the nearest topic I could find was centered around dicussions in respect Nlite and a version of Dotnetframework that had been "thinstalled or Thinapped" Sorry about the terminology but I think the majority will catch my drift???
Any thoughts or observations negative or positive woud be welcomed!
Regards & Best wishes,
ispy
![;)](http://reboot.pro/public/style_emoticons/default/wink.png)
P.S. All the very best to all Boot-land members at this Christmas festive time & remember don't forget about the real meaning of Christmas. For God so the World.... (That means each & every one of us as individuals)
addendum - Kewl new web site Nuno!!!