You can open the source code for Gallery Server Pro with any of these products:
Visual Studio 2005
Visual Studio 2008
Visual Web Developer 2008 Express with SP1 (
free download from Microsoft)
Visual Studio 2005:1. Download the source code and extract the directories and files to the desired location.
2. Use Visual Studio 2005 to open TIS.GSP.sln.
3. That's it! The solution should compile, and if you right-click installer/default.aspx, Visual Studio will use its internal web server to start the installer to help you connect the app with the database.
Visual Studio 2008 and Visual Web Developer 2008 Express with SP1:1. Download the source code and extract the directories and files to the desired location.
2. Start Visual Studio and open TIS.GSP.sln.
5. The upgrade wizard will start. Step through the wizard until it is finished.
6. That's it! The solution should compile, and if you right-click installer/default.aspx, Visual Studio will use its internal web server to start the installer to help you connect the app with the database.
Notes:1. When I tested the source code in Visual Web Developer 2008 Express with SP1, I received the following message at the end of the upgrade wizard:
Quote:Some of the properties associated with the solution could not be read.
I am not sure of the implications of this, but the code still compiled and seemed to work fine. Let me know if you can add any insight into this.
2. Compiling the source code copies the 64-bit version of System.Data.SQLite.dll to the web application's bin directory, even though I changed the project reference to specify the 32-bit version just before releasing the source code. This will cause an error when you try to run Gallery Server Pro on a 32-bit operating system. To resolve this, open the project TIS.GSP.Data.SQLite and delete the 64-bit version of the dll - it is in the directory assemblies\x64.
3. You may get this error when running Gallery Server Pro for the first time:
Quote:The base class includes the field 'ScriptManager1', but its type (System.Web.UI.ScriptManager) is not compatible with the type of control (System.Web.UI.ScriptManager).
This can be resolved by converting the web application to .NET 3.5. (It may be possible to resolve it and still stick with .NET 2.0, but I haven't had the time to dig in.) Right-click the gsweb project in the Solution Explorer (on the right side in Visual Studio) and click Properties. On the Application tab, select .NET Framework 3.5 in the Application Target dropdown box. Click Yes when asked to confirm.
Roger Martin
Lead Developer for Gallery Server Pro