I wanted to write about some issues I am facing and some fixes I have found in using SQL Server 2005 with rainbow.  I guess you could use these same fixes with any .NET 2.0 application with SQL Server 2005.

One issue I was having was connections to SQL Server 2005 express not connecting with Integrated Security.  Personally, I like IS because it only uses the machine for auth and not some outside account.  This makes me feel more secure when I deploy applications.  Also its an easier connection string ;).  If anyone out there has a better way, Im all ears [ and by better I mean more secure].  Basically, if you use windows 2003 and want to use Integrated Security = true option, you MUST create a user in SQL Server 2005 for NT\NETWORK SERVICE.  Once I did this, all my problems were over.  I easily installed jon's new precompiled code into SQL Server Express without even touching VS 2005.  Thats right kids.  If you know how to use SVN, you can easily just down the code, change the connection string to SQL Server 2005 Varient [ all seem to work from developer to express], IIS the directory to http://localhost/Rainbow and browse to the directory.  Seems like a mouthfull but for normal developers and experienced users, this takes only 5 minutes.  I constently deploy about 3 new versions a day of Rainbow 2.0 Alpha for core test.  I welcome you to start using some of the .NET options such as partial classes.  Copy and paste ASP.NET 2.0 code in the component module or build an Asynchronous Gridview in seconds.


Another Issue I deal with is VS 2005 relative paths.  I found out that in VS 2005 they really make it nice for relative pathing.  You can place rainbow anywhere and it will work.  However, if you want to develop on rainbow, you will have to go a step futher.  You will have to tell each project to output its new dlls to your rainbow install [ wherever you might have it].  This way, when you develop lets say on your own core; your code will be deployed to the right folder.

Another thing I stumbled on was check your logs eventhough you get a good install.  I checked my log one day right after I had a successful install and I found that one of my modules didnt even install.  It was written in the log as a warning and just by passed.  It was the google search engine and I happen to love google.  Im lucky that it wasnt a client user module and I will learn that every deployment to look at my log.  Would be a nice option to have the log viewable in a gridview or xml snapshot right after install.

As Jon produces version after version in the SVN, we continue to get closer to our core being strong enough for possible release.  ALL of the core functionality are in assemblies.  Rainbow now has its personal APP_Code files for precompile.  We currently have around 10 projects and we realize this is a lot.  Jon is consolidating and I am helping by organizing the code for release level quality as well as correting/fixing/googling issues :).  His next code commit promisses to be an even more refactored core.  Manu is also comming back to us and March looks promising.

We look forward to hitting our developer date of March 1st.

Cheers,