←  Announcements

AutoPatcher Forum

»

**Working** Dotnet Addon Pack Coming Soon

Erik Ramey's Photo Erik Ramey 11 Dec 2007

***Update***
The new dotnet addon pack is now up and running 100 percent

-------------
I wanted to let everybody know that all the dotnet modules have been removed from the scripts in order to make room for the new dotnet addon pack that will be going live soon. (Next day or so) The new dotnet pack will include all main dotnet releases including dotnet 1.1, 1.1sp1, 2.0 sp1 for Windows 2K, plus 3.5. This pack will also be compatible with all OS's that AP supports including x64. Keep an eye out for it B)
Quote

sh1leshk4's Photo sh1leshk4 11 Dec 2007

...and here I thought you already had the script working! xD

Well, it should be a relief for admins going lite since now they virtually can't opt out d/l-ing what's not considered an add-on whenever they start from a clean AP folder.

Ok, this is OT (and sorry for that), but how about getting the Flash players as add-ons too?
The add-ons are, after all, now a "unified" download instead of separate files like in AP of the past.
(...assuming apup.exe doesn't stop d/l-ing midway anymore... ;))
Quote

Erik Ramey's Photo Erik Ramey 11 Dec 2007

 sh1leshk4, on Dec 11 2007, 01:28 AM, said:

...and here I thought you already had the script working! xD

Well, it should be a relief for admins going lite since now they virtually can't opt out d/l-ing what's not considered an add-on whenever they start from a clean AP folder.

Ok, this is OT (and sorry for that), but how about getting the Flash players as add-ons too?
The add-ons are, after all, now a "unified" download instead of separate files like in AP of the past.
(...assuming apup.exe doesn't stop d/l-ing midway anymore... ;))
No worries, that's a commin too. For now I wanted to get flash, shockwave, and java out there right away since it's so popular. Also I didn't want to create an addon pack with only two or three items in it. Expect the ole' AP Add-on pack later this week after all the Tuesday patches are added.
Quote

James's Photo James 11 Dec 2007

That's great news, Eric, since only about a quarter of the 24 computers I manage have any form of dotNET on at all!
--
James
Quote

Rudy's Photo Rudy 12 Dec 2007

runtime error(0) on file not found for dotnet add-on

AutoPatcher Updater starting.
List file HTTP location: http://www.autopatch...m/releases.list
Download queue status: 1 files waiting.
releases.list: Download complete.
Download queue status: 0 files waiting.
Download queue status: 1 files waiting.
autopatcher_dotnet_enu.script: 404 File not found
Quote

StanTheMan's Photo StanTheMan 12 Dec 2007

 Erik Ramey, on Dec 11 2007, 08:49 AM, said:

I wanted to let everybody know that all the dotnet modules have been removed from the scripts in order to make room for the new dotnet addon pack that will be going live soon. (Next day or so) The new dotnet pack will include all main dotnet releases including dotnet 1.1, 1.1sp1, 2.0 sp1 for Windows 2K, plus 3.5. This pack will also be compatible with all OS's that AP supports including x64. Keep an eye out for it B)


Do we need to delete our existing dotnet files when the new dotnet addon pack is available or will apup sort it out for us?
Quote

Erik Ramey's Photo Erik Ramey 12 Dec 2007

 StanTheMan, on Dec 12 2007, 11:22 AM, said:

Do we need to delete our existing dotnet files when the new dotnet addon pack is available or will apup sort it out for us?


No need to do anything. Basically if you already have downloaded dotnet from any previous pack, you won't be prompted to download again. All the scripts for dotnet from the Windows 2K, XP, and x64 were migrated into one pack B)
Quote

Erik Ramey's Photo Erik Ramey 12 Dec 2007

Just a heads up for everybody. The DotNet Pack is now on the list within APUP but I need to update the scripts name. ETA of fix about eight hours from now =)
Quote

sh1leshk4's Photo sh1leshk4 12 Dec 2007

Take your time...it's not good to stay cooped up in a room just to write some scripts.... ;)
Quote

Rudy's Photo Rudy 13 Dec 2007

 sh1leshk4, on Dec 13 2007, 10:04 AM, said:

Take your time...it's not good to stay cooped up in a room just to write some scripts.... ;)

yes agree, light a fire and put some meat on and open a couple of cool stuff and then the scripts would come good.
Edited by Rudy, 13 December 2007 - 05:13 AM.
Quote

DesertJerry's Photo DesertJerry 13 Dec 2007

Good work all.

Ran APUP - noticed Dotnet addon pack included in release; Next resulted in Runtime error '0'.

Deleted all scripts, tried again - runtime error '0'.

Unchecked box for DotNet addons - downloads started and got one verification/continue message - clicked ok.

Ran APUP and left check mark in Dotnet Addon box - Runtime error '0' again.

Reran APUP, unchecked Dotnet addon - download started for Falsh Player install/uninstall from Macromedia (Adobe) - got Runtime error '0'.

Ran through everything again and got same results.

Hope this helps.
Quote

DesertJerry's Photo DesertJerry 13 Dec 2007

Also, since we're talking about DotNet:

Should these also be included in the Dotnet Framework addon?

PowerToys for NET Compact Framework 3.5
Parallel Extensions To NET Framework 3.5

I found them on the Microsoft download site between 5 and 10 December.
Quote

Rudy's Photo Rudy 13 Dec 2007

 DesertJerry, on Dec 13 2007, 03:20 PM, said:

Good work all.

Ran APUP - noticed Dotnet addon pack included in release; Next resulted in Runtime error '0'.

Deleted all scripts, tried again - runtime error '0'.

Unchecked box for DotNet addons - downloads started and got one verification/continue message - clicked ok.

Ran APUP and left check mark in Dotnet Addon box - Runtime error '0' again.

Reran APUP, unchecked Dotnet addon - download started for Falsh Player install/uninstall from Macromedia (Adobe) - got Runtime error '0'.

Ran through everything again and got same results.

Hope this helps.

Hi DesertJerry

see my post #5 in this thread runtime error(0) on download
according to Erik, it would be fixed soon
Edited by Rudy, 13 December 2007 - 05:12 AM.
Quote

Erik Ramey's Photo Erik Ramey 13 Dec 2007

I wanted to mention in this thread too. I forwarded a new release.script over to Renato who will upload the script later tonight. Sorry for the inconvenience everybody
Quote

Renato's Photo Renato 13 Dec 2007

The script was updated, so, it should work fine now.
Quote

StanTheMan's Photo StanTheMan 13 Dec 2007

Hmm, 404 file not found!!

AutoPatcher Updater starting.
List file HTTP location: http://www.autopatch...m/releases.list
Download queue status: 1 files waiting.
releases.list: Download complete.
Download queue status: 0 files waiting.
Download queue status: 1 files waiting.
autopatcher_dotnet_enu.script: 404 File not found
Quote

StanTheMan's Photo StanTheMan 13 Dec 2007

It now downloads the dotnet2.0sp1 fine. But i get another file verification error!

Looking for file C:\apup\modules\Components\__dotnet\dotnet3.5_enu.apm
MD5 Hashes do NOT match. Expecting 89205a7b98b191a1d46c21ca5d20cfc9, but found 19bfd0c211fd85be41bdcab0910c3aae!!!

Thanks!
Quote

Erik Ramey's Photo Erik Ramey 13 Dec 2007

Fixed. Should be working 100 percent now
Quote

Rudy's Photo Rudy 13 Dec 2007

Hi Erik,

great - working 100% now.
Quote

Cyrus's Photo Cyrus 13 Dec 2007

 Erik Ramey, on Dec 13 2007, 10:08 AM, said:

Fixed. Should be working 100 percent now
Not on my computers, they (I tested it on several) still get the same MD5 error as before.
Quote