2.5 Package Documentation

Sep 6, 2009 at 4:03 PM

I think it would be really useful to provide better installation documentation.

Initially I had decided to the get just the deployment package, since I did not think that changing any code was necessary to begin with. I had some issues trying to set it up, so I decided to download the full source code version.

Once I opened up the solution, I realized that things were completely different. For instance in the source version, all configurations are bundled in the web.config, while in deployment version they are not. Furthermore, the connectionstring name in the source is also different that the one in the deployment package (KIGGDatavase in source, VS KiGGSqlServer in the deployment version). 

I still have not finished setting this up as I am still try to figure out all the lose ends, but some help would be really helpful. Maybe it is just a matter of doing some clean-up in the packages?



Sep 6, 2009 at 4:21 PM

In case this helps anyone...

If you are downloading the deployment package (not the source).... you will need to do this:

1. If you are using the SQL database connection string, make sure that the connection name is "KIGGDatabase", not KiGGSQLServer)
2. The unity.ef.config file is broken. You will get EF error trying to run the default one in the package. Here is what I did:

a.  I downloaded the source version of the package.
b. Opened Web.Config, and copied the entire UNITY section.
c. Pasted it in the Unity.ef.config file.

Once I did that, I was able to pull up the site.

Hope this helps.


Sep 6, 2009 at 4:43 PM

Ok - so, as I dig into this further, I find more information.

Basically the problem with the default Unity.ef.config (using SQL Server connection) is the fact that there as some EF related configuration settings that need to be removed.

Around line # 518, you will see the IConnectionString node. You will also notice that you will find the following:

<param name="edmFilesPath" parameterType="System.String">
                  <value type="System.String" value="|DataDirectory|"/>
                <param name="ssdlFileName" parameterType="System.String">
                  <value type="System.String" value="DomainObjects.SqlServer"/>

Essentially, you need to remove those entries.


Sep 7, 2009 at 1:29 AM

I will test the deployment package again! I made it from a published site after testing. But note something there is Unity.l2s.config where what you mentioned in the last thread is correct as you don't need the edm stuff.

You are right we should provide some documentation for better installation and deployment. Hopefully to be done during this month.

Sep 7, 2009 at 3:44 AM

Thanks Mosessaur,

We just upgraded and went live on 2.5 at www.pimpthisblog.com. So far so good. You should probably highlight that an ASP.net MVC upgrade should also be done prior to *upgrading*. Some of us were still running with the CTP bits :-)

So far so good though. I'll keep an eye open.

Oh, and BTW, the documentation should probably include some information to turn off the verbose logging that goes one.


Sep 8, 2009 at 12:20 PM

I will do my best to include detailed documentation.

Btw, KiGG 2.2 version was updated to MVC RTM. v2.5 was built on top of it. Didn't know that this caused an issue, because so far I didn't touch ASP.NET MVC and the updates on v2.5 for it almost none except for DotNetOpenAuth.

Will start with documentation next month I guess, and if lucky next week :o).

Sep 10, 2009 at 9:30 PM

I'll try to contribute some to that since I have to upgrade my own sites and I may have more to launch.

Sep 13, 2009 at 12:26 AM

Just figured I'd jump in here, as I've been having some similar issues as well:

1. Can I request that you include separate documentation (readme.txt) for the deployment version versus the source code version.

2. Can I request a list of requirements be included in the readme.txt. For example, I did not have ASP.NET MVC installed and while I did have SQL Server 2008 installed I had not installed with Advanced Services (e.g. for full-text).

3. I'm still having some problems with the deployment package. I have the database configured but when I open the deployment package and choose to Debug (in VWD) it just brings up a listing of the folders. I also get a long series of messages about: "Could not find schema information for the element:" (loggingConfiguration, configSource, and so on).

Any assistance is appreciated! Thanks.

Dave Mackey.

Sep 13, 2009 at 6:56 PM
Edited Sep 13, 2009 at 6:58 PM

Hi David

Regarding point 1, I didn't understand the part of deployment version vs source code version! Could you please clarify more

For point 2, you are right! this should be included as part of system requirements. I will do it on online documentation and will be added to offline readme.txt file as well.

And for point 3 it is my first time to face this issue, I couldn't reproduce it! because if you followed the steps in the [Deployment Guide Part 1] such issue won't appear, unless there is something missing!|
Note that the deployment package is in release mode and debug is turned off on web.config. This might be one of the reasons but not sure.

Sep 15, 2009 at 6:04 AM

In point one, I simply meant to create a separate readme.txt file for the deployment and source code versions - that way you don't have instructions in the readme that apply only to the other form (e.g. instructions for the source code version in the deployment readme.txt).

In point three - I am now only getting warnings, so that is fine. My real problem now is that when I run the application (in VWD Express) it takes me to a directory listing. I don't see any static pages even in the project? Is a default template not included? Thanks.


Nov 5, 2009 at 5:02 PM
Edited Nov 7, 2009 at 3:02 AM