Hi All,
Looking at putting a dev environment together for SolidCP.. does anyone have any notes or anything at all that gives a little more than the "How to build source" page? Anything at all.. just a line of wisdom would do. The 'how to build page' finished with "You will now see.... " and left if there LOL.
A couple of more specific questions if anyone has the time to reply...
- The https://solidcp.com/kb/development/how-to-build-source/ page says you need three SDKs for .net - but the download pages the links on there point to no longer exist.. so it leads me to wonder what of those SDKs are really needed. What are people doing..? using an old copy of those SDKs or something more up to date now?
- It says Web Deploy 3.6 but that seems to break some stuff in SolidCP when installed on the server... I found a note on the forum to use 'Web Deploy for Hosting' instead which works... is that what you're using for dev?
- Are you primarily using VS 2019 now?
- Wasn't there a WSP development guide? Does anyone still have a copy of that hanging around?
Many thanks in advance 🙂
Hoping I can lend a hand and get stuck in.. long time .net developer with a lot of experience of Windows hosting (since IIS2 lol).
Cheers - Mark
Hey,
First i would recommend as CLA to use the contributors chat (it will give more quick answers most of the day).
Other then that: make sure you have web deploy 3.6 installed (anything higher will cause errors on build, in some cases you have to un-install the higher version 2x web deploy 3.6 for hosting will do just fine too).
Basic method i use to setup our dev lab is to first install SolidCP as normal (portal/enterprise/server(s) etc) using the installer.
Then download the source with git, setup your master repo and your fork repo (so you can pull changes from master to keep your own dev codes up2date).
Make a full build using the build-release.bat and make sure it doesn't error.
In iis --> re-assign the site paths of portal / enterprise / server to your git source (not de deploy dir but actual source dir).
overwrite your web.configs and scheduler config with the ones created by the installer, make sure the sites don't error and you should have your self a live dev environment.
We currently still use vs 2017 primarily but will start on making that into 2019 shortly.
Wsp deployment guide - not sure the problem at the time was that the websitepanel site, even the source got removed 99% (we where one of the last ones with the latest wsp 2.1 source at that time).
It's the main reason SolidCP was created - to not let WebsitePanel vanish from the world.
Regards,
Marco
Thanks Great, thanks Marco. I'll try to document as I go along.
That would be great thanks 🙂
(our documentation as you have noticed is quite behind.. always too many other things to do).
