Web Designer work and deploy with solution project

You can configure and use this to your needs.

It is technically possible to have one solution project for each staging. In each environment you just link to the file path.
As the complete web application is in DialogScriptAssembly there is technically no need to import the files to the database.
There is a wizard in Web Designer to do the import.

Bringing the code from DEV to TEST to PROD it might be a matter of taste and project documentation, if you prefer the Transport or the import wizard with the Source Control.
Working with the solution or database project is also a matter of taste and project documentation in the different staging environments.
The import Wizard has no ChangeLabel, so another matter of taste and project documentation.

I think you have to try it out and find out your way. There will be differences because of customer requirements, how many web developers, long term web developers, a lot of changing web developers, minor project documentation, minor competence....

Hi Geraldine

If possible, I want to use the solution project, since I like to have files in version control and have to possibility to do branching.
And I want to have a deployment from stage to stage without manual intervention.

Do I understand that correctly:
If I want to bring the solution project from DEV to TEST to PROD I have options:
1. Import into database, create a Transportpackage
2. Open the solution project in each stage in WebDesigner and publish it.
3. Open the database project in each stage in WebDesinger and import a selection of xml files from the solution project.

Option 1 would have the drawback, that the files in the solution could be different to the object in the db.
Option 2 and 3 would mean manual intervention in the deployment process, which we want to avoid at all.

To be honest: I don't really understand by now how the solution project really works. The documentation explains the most obvious steps in detail, but I don't see the concept behind.

Patrick

btw:
In the meantime I've done some experiments with \VI.WebDesigner.CompilerCmd.exe

It was possible to start it but I've got errors, since the solution project doesn't contain the VI_... files.
Therefore I've got the error:
Info: Enhanced checks: False, mode: Normal, debug: True
Info: Compiler Main created
Warn: Requested compilation object was not found: VI_Start, this is not necessarily an error
Warn: Requested compilation object was not found: VI_Session, this is not necessarily an error
Info: Compiler started: Main
Info: Compiler stats: 27 steps, 7 on thread pool, steps per level: 8, 13, 6
Info: Compiler took 15.606 ms
Info: Compiler generated 2 items, 18 errors
Warn: First 10 compilation errors:
Warn: Object reference not set to an instance of an object., VI.WebDesigner.Definition.Include.RendererSettings, CCC_Web Object reference not set to an instance of an object. at
VI.WebDesigner.Loader.CompilerBase.CompileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., VI.WebDesigner.Definition.Include.RendererSettings, CCC_Web Object reference not set to an instance of an object. at
VI.WebDesigner.Loader.CompilerBase.CompileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., VI.WebDesigner.Definition.Include.RendererSettings, CCC_Web Object reference not set to an instance of an object. at
VI.WebDesigner.Loader.CompilerBase.CompileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., VI.WebDesigner.Definition.Include.RendererSettings, CCC_Web Object reference not set to an instance of an object. at
VI.WebDesigner.Loader.CompilerBase.CompileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., VI.WebDesigner.Definition.Include.RendererSettings, CCC_Web Object reference not set to an instance of an object. at
VI.WebDesigner.Loader.CompilerBase.CompileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., VI.WebDesigner.Definition.Include.RendererSettings, CCC_Web Object reference not set to an instance of an object. at
VI.WebDesigner.Loader.CompilerBase.CompileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., VI.WebDesigner.Definition.Include.RendererSettings, CCC_Web Object reference not set to an instance of an object. at
VI.WebDesigner.Loader.CompilerBase.CompileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., CCC_Web (0), CCC_Web Object reference not set to an instance of an object. at VI.WebDesigner.Loader.CompilerBase.Com
pileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., CCC_Web (0), CCC_Web Object reference not set to an instance of an object. at VI.WebDesigner.Loader.CompilerBase.Com
pileBindingItem.<CompileAsync>d__3.MoveNext()
Warn: Object reference not set to an instance of an object., CCC_Web (0), CCC_Web Object reference not set to an instance of an object. at VI.WebDesigner.Loader.CompilerBase.Com
pileBindingItem.<CompileAsync>d__3.MoveNext()
[System.Exception] WebDesigner compiler reported errors.

Please load your CCC_Web to the database.
This is necessary, as QBMWebApplication can only point to something in the database.
But yes the CMD compiler is no built to compile a solution project.

OK, than my approach for deploying the solution project to the next stages would be.

1. Load the files from the solution by script into the corresponding DialogAEDS entries.
2. use the CMD compiler to compile the webproject in the database

hmm... that won't work.
I just realized that the customization as extensions isn't part of the solution project.

I have to find another way.

The solution project in the context of deploying to other stages doesn't make sense at all from my point of view, since CustomConfiguration in standard components wouldn't be covered.