• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 95 subscribers
  • Views 5126 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Web Designer work and deploy with solution project

prueegg
over 7 years ago

Hi

 

I'm working with V7.1.1 and for the Web Designer we always used Database projects.

Since a file based solution has some big advantages (source control) I take a look at the "solution project".

 

I saw, that it is possible to import/export solution projects in the webdesigner. What I'm not sure is, wo I have to transport the "solution project" from one stage to the other.

Do I have to import it in DEV into Database and transport it via normal Transportpakages? Do I have to import the files in each stage manually in the WebDesigner?

Or is there a way to automate the import of the new files from the solution project in each stage?

Parents
  • 0 over 7 years ago
    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....
Reply
  • 0 over 7 years ago
    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....
Children
No Data