I ended up writing a Windows application that would execute svcutil through a graphical interface. You can find the application source code and installer on codeplex here:

http://graphicsvcutil.codeplex.com/

For the application to work correctly it is required to have the svcutil.exe file installed with the developer SDK in the default location. It also assumes the usage of the default configuration file for the code creation process. I am planning on enhancing the application in the future by adding the capability to choose the configuration file.

If any one is interested in adding that part themselves, just email me so I can add you to the project team in codeplex.

I want to start working on a similar project with stsadmin but that command has far more switches then svcutil.

I than tried to open my solutions and add them to a project on the server. I ran into an interesting problem. On some of my solutions I did not get the “Add Solution to Source Control” option to show.

I came to find out that if you had a solution that was previously added to a team foundation server you can not seemingly disconnect that solution from the old server and re-add it to the new one.
You will have to edit the “.sln” file with a text editor. First remove the read only attribute that is attached to most solution files. Then open it in a text editor and delete the section between the “Global” and the “EndGlobal” tags.

   1: Global

   2:     GlobalSection(TeamFoundationVersionControl) = preSolution

   3:         SccNumberOfProjects = 2

   4:         SccEnterpriseProvider = {4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}

   5:         SccTeamFoundationServer = http://psiserver2:8080/

   6:         SccLocalPath0 = .

   7:         SccWebProject1 = true

   8:         SccProjectUniqueName1 = http://localhost/eShopAdmin2

   9:         SccProjectName1 = eShopAdmin2

  10:         SccLocalPath1 = ..\\..\\..\\..\\..\\..\\inetpub\\wwwroot\\eShopAdmin2

  11:         SccProjectEnlistmentChoice1 = 2

  12:     EndGlobalSection

  13:     GlobalSection(SolutionConfigurationPlatforms) = preSolution

  14:         Debug|Any CPU = Debug|Any CPU

  15:     EndGlobalSection

  16:     GlobalSection(ProjectConfigurationPlatforms) = postSolution

  17:         {6A136601-523A-4F5B-A9E4-E281CB337B43}.Debug|Any CPU.ActiveCfg = Debug|Any CPU

  18:         {6A136601-523A-4F5B-A9E4-E281CB337B43}.Debug|Any CPU.Build.0 = Debug|Any CPU

  19:     EndGlobalSection

  20:     GlobalSection(SolutionProperties) = preSolution

  21:         HideSolutionNode = FALSE

  22:     EndGlobalSection

  23: EndGlobal

Then save the file and reopen the solution with VS2008. You may receive a message notifying you that the solution is no longer attached to a Team Foundation server and asking you if you want to completely remove the solution from source control. Press “Yes” to remove the solution from source control. You can now re-add your solution to your new Team foundation Server.

I still run into a problem when I try to add a new project to the server but per MS that would be fixed in a future update to VS 2008. I now just need to figure out how to delete a project from the new Team Foundation Server.

The authentication event can extract the user supplied credentials and authenticate against a database or any other method of your choise. My authentication method looks like this:

protected void ctrLogin_Authenticate( object sender, AuthenticateEventArgs e )
    {
        string strUserName = ctrLogin.UserName.Trim().ToString();
        string strPassword = ctrLogin.Password.Trim().ToString();
        int nUserId = 0;
        int nUserSecurity = 0;

        DataClassesDataContext dtx = new DataClassesDataContext();

        var vAdminUser = from au in dtx.t_admin_users
                         where au.user_name == strUserName && au.password == strPassword
                         select new { au.user_id, au.security_id };

        if ( vAdminUser.Count() == 1 )
        {
            nUserId = vAdminUser.Single().user_id;
            nUserSecurity = vAdminUser.Single().security_id;

            if ( nUserId != 0 && nUserSecurity != 0 )
            {
                Session.Add( "user_id", nUserId );
                Session.Add( "user_security", nUserSecurity );
                e.Authenticated = true;
                FormsAuthentication.RedirectFromLoginPage( nUserId.ToString(), true );
                Response.Redirect( "AdminHome.aspx");
            }
        }
    }

Notice the line:

 FormsAuthentication.RedirectFromLoginPage( nUserId.ToString(), true );

this line forces the creation of the client side cookie letting the ASP server knows the client is authenticated. With out this cookie the server will not see the clent as an authenticated user.

setting the web config with the following setting will ensure that all pages in your application will forward their request to the login page if the authentication cookie does not exist or is expired on the client.

<authentication mode="Forms">
      <forms loginUrl="AdminLogin.aspx" timeout="30">

      </forms>
    </authentication>
    <authorization>
      <deny users="?"/>
    </authorization>

Last tip that I can add is if you want the missing password and missing user name errors to show up when a user tries to submit the login control with out any of those credentials, you will need to add a group validator and set the ValidationGroup to be the same id as your login control.