Developer forum

lb wrote:

Hi

 

Om my request DW Helpdesk har created a new document telling how to do basic upgrades of Dynamicweb.

 

That document is now available on downloads - perfect :)

 

But now for the tricky stuff:

 

I know there are some scripts to be run as well by the angel account.

I've done that, but what do they do ?

 

I would think they do database upgrades ?

E.g changes in data, adding new fields to tabels etc - and/or ???

 

And what about old solutions ?

F.ex i have one now running on 18.14.1.0 from 20-05-08.

Can i just trow in the newest DLL's and run the update scripts ?

 

 

 

/Lars 

 

Hi Lars
 

angel does not have to run some scripts - dynamicweb will handle that automatically when you add a new version of the application to a website.

Inside /Admin there is a xml file with all DB and filestructure changes made since break of dawn. Each set of changes have a version number - when you copy a new application to a running Dynamicweb, the application will take a look at /Files/Update.xml - in that file the current fileset version number is found - Dynamicweb compares to whatever is found in the new /Admin and applies the missing updates.

So - you cannot just throw in the new dll's - they would require some of the new fields. So before doing that, make sure that /Admin has been updated first - then the dll's. 

So - just to make shure i understand:

1. Update the DDL's in /admin - thus causing the update script to run

2. Check that out via backend.

3. Update the DLL's in the /Application/bin

Will it be equally ok to do:

1. Install a fresh /admin

2. Change the solution admin folder to point at that

3. then update the /Application/bin

I assume that when you have several solutions sharing the admin folder, the level on the database and other is situated in the /Files/Update.xml ?

And if i understand this right, it should present no problem to upgra a soulition from 20.05.2008 ?

/Lars

There are no dll's in /Admin - so allways up-date the entire folder - either by overwriting it or by changing the location in IIS. Then up-date the bin. It will up-date the entire solution, and it wil work on all Dynamicweb ASP and .NET installed after may 2002.

Hi

Ok - i ment /Admin/bin :o)

But i got the meaning - thanx..

/Lars

lb wrote:

Hi

 

Ok - i ment /Admin/bin :o)

 

But i got the meaning - thanx..

 

/Lars

There aint no /Admin/Bin.

Ahh.

Now lets see:

I have the following on my partner server::

Dynamicweb.net/Application/bin

Dynamicweb.net/Application/admin

The /bin is the runtime DLL's used by the frontend - correct?

The /admin is the one in question

The above here is the common Admin and application folders for all installations ? (The ones that use them at least ;o))

Looking at my partnerserver for the same solution, i have additional two Application folders for the same solution in more than one place, (Under solutions and SolutionsCustom) but that is probably due to historic reasons ( a bit messy though ;o))

But the only right thing is to look on the IIS where to finde the rigth folder...

Thanx for the insight..