In the first episode, I tried to install SQL Server 2008 RC0 Advanced Express (with only the database engine and Management Studio)...but the result was "Error 1814" during service starting.

First action : "Repair"...but not possible because the program can only repair a well performed installation.

In this second episode, I tried to uninstall the database engine service that previously failed and then try to reinstall it !!!

 

Uninstalling...

Reinstalling...

 

 

This time, the installation succeeded !

To resume the differences between the first and the second installation (before --> after) :

• Selected features : Database only --> Database + Full text search
• Account for database service : NETWORK SERVICE --> SYSTEM
• Collation : French_CI_AS --> Latin1_CI_AI

I have operated this change for the following reasons :

• Full text search : the error's description was talking about "dependency problem"...I tried to add the classical service associated with SQL Server
• System Account instead of Network Service : the error's description was talking about "file write or access problem"
• Collation : this is a Release Candidate and recurrent problem with beta versions are associated with language problem (being full English is always better !). For information, I have installed SQL Server on a French Windows Vista system.

I will try to find the real root cause...

Previously installed :
- .NET Framework 3.5
- Windows Installer 4.5

Tested prerequisites :

Installation dashboards :

Planning


  

  

Requirements details on Microsoft site : http://msdn.microsoft.com/en-us/library/ms143506(SQL.100).aspx

Stand alone installation steps of the SQL Server 2008 Advanced Express

Licensing

 

Installing setup support files

 

Defining features et settings

Installation summary and starting...

 

Database installation succeeded but service starting failed ! Error 1814...

Let's see the second episode on the next post !

Previous versions of "Dynamic Data" were designed to use "LinqToSql".
With this service pack beta, you can use it with "Entity Data".

The "Context" type that must be declared is now "ObjectContext" instead of "Datacontext".

After having installed...
- .NET Framework 3.5 SP1 Beta
- Visual Studio 2008 SP1 Beta
(can be download here for .NET and here for VS)



...you can create a new project "Dynamic Data Entities Web Application".



Then you just have to :
- Create an "ADO.NET Entity Data Model" (for instance with the context class named "MyModelEntities") and insert one or more tables.



- Uncomment and change the specific line in "Global.asax.cs" :

model.RegisterContext(typeof(MyModelEntities), new ContextConfiguration() { ScaffoldAllTables = true });

- Launch the project

SQL Server Management Studio Express is a limited version that authorize access to SQL Server Databases (Express or not).

Analysis, Reporting, Integration Services or SQL Server Agent are not available from this Express version.

Most important features from  "Databases" and "Security" trees are available to create and modify databases and security accounts (but not roles).

The following features are also available:

- Generate scripts

- Attach/Detach

- Backup/Restore 

- Activity monitor

...whereas "Maintenance plans" and "Logs" can't be opened.

 

The prerequisites are at least : 

Microsoft Data Access Components (MDAC)                3.70.1146
Microsoft MSXML                                        3.0 5.0 6.0
Microsoft Internet Explorer                            6.0.2800.1106
Microsoft .NET Framework                               2.0.50727.42

• Install this VS 2008 update : KB945282. Download it here
• Install ADO.NET Entity Framework Beta 3. Download it here
• Install ADO.Net Entity Framework Tools Dec 07 Community Technology Preview. Download it here
• Watch "ADO.NET Entity Designer Video - CTP 2" video here

• Install "GuidanceAutomationExtensions -  July 2007 CTP". Download it here (this version can be attached to VS 2005 or 2008 Orcas)
• Install "Software Factory - Modeling Edition Feb 2008 CTP". Download it here (this version is attached to VS 2008)
• Apply this fix to avoid the following error "Project Creation Failed" from Visual Studio 2008 while creating a new project. This is due to some assembly redirects that are added to the devenv.exe.config file by installing the GAX (Guidance Automation Extensions).

• Open "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.config" from notepad
• Comment the line containing this string: "Microsoft.VisualStudio.TemplateWizardInterface"

      <dependentAssembly>
        <!– <assemblyIdentity name="Microsoft.VisualStudio.TemplateWizardInterface" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /> –>
        <bindingRedirect oldVersion="0.0.0.0-8.9.9.9" newVersion="9.0.0.0" />
      </dependentAssembly>

• Close and re-open Visual Studio 2008, and try to create a new project

• Watch the following introduction : 15 minutes walkthrough

Minimum prerequisites :

- Windows Server 2003 SP1 or R2 or Windows Server 2008
- IIS 6 or IIS 7
- .NET Framework 2.0
- SQL Server 2005 SP1or SP2 or  SQL Server 2008 with collation constraints (these options are NOT supported : Accent Insensitive, Case sensitive, Binary, Binary2)
- SQL Server Analysis Services
- SQL Server Reporting Services (not need to configure it, TFS installation will do it for you)
- MSXML 6.0 Parser SP1 (download here)

Possible prerequisites :

- .NET Framework 3.5
- Windows Sharepoint Services 3.0

What will be installed by TFS 2008 setup program :

- .NET Framework 3.5
- Windows Sharepoint Services 3.0 (setup ask for installing WSS 3.0 or using a existing instance)
- Microsoft Visual Studio 2008 Team Foundation Server

Sample screenshots :

The others modules that could be installed are :

Delivered on the same DVD

• Team foundation server proxy
• Team foundation build
• Team explorer (on a development server, you can install "Visual Studio 2008 Team Suite (or Development, architect…)" before installing Team explorer and then, in a second time, install Team Explorer that will update you Visual Studio 2008 environment. I only tried this scenario and it works fine)
• Windows Sharepoint services extensions

Downloadable on Microsoft site

• Visual Studio Team System Web Access 2008 Power Tool (download here)

Sample screenshots :

Windows Sharepoint services extensions	Team System Web Access 2008

 

Complete installation scenario of a development platform for Team system 2008

 

 

• Install Windows Server 2003 R2
• Add application server role (without FrontPage extensions and with ASP.NET)
• Install SQL Server 2005 SP1 with collation by default (accent sensitive, case insensitive) and by selecting : Analysis Services, Reporting Services
• Install MSXML 6.0 Parser SP1
• Install Team Foundation Server 2008 (it includes .NET 3.5 and WSS 3.0)
• Install Windows Sharepoint services extensions
• Install Visual Studio 2008 Team Development
• Install Team Explorer 2008
• Install Team System Web Access 2008

 

 

As Visual Studio 2005 can do while referencing a registered COM library, you can use the following scripts to automate the creation of an interop :

"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\tlbimp.exe"
MyLibrary.dll
/out:Interop.MyLibrary.dll
/namespace:NewRootNameSpace
/keyfile:MyLibrary.snk
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.data.dll
/reference:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.xml.dll
/verbose
/asmversion:1.0.0.0

(If necessary, add reference options)

For a recall, the strong named key is created with :

"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -k MyLibrary.snk

Don’t forget to register the library with regsvr32.exe before executing the first script

WARNING ! For COM library created from VB and using instructions like ReDim, it is useful to add the option :  /sysarray to have System.Array declared (for intance : instead of string[] for String() VB parameters).

Since a long time, I was searching for a free and complete text editor to install on all my machines. I think this one will become my new friend !

The famous one that would resolve my problems is probably Notepad++. 

The interesting features are (for me) the following ones :

• XML editing (to collapse nodes and include syntax coloration…)
• "All" programming language coloration
• Having a hexacidemal view of the content (hex edition)
• Evaluate or change text encoding
• Advanced search and replace features (a lot of options…with "light" regular expression possibilities)
• Extensible through plugins
• Multi document management
• And ultimate pleasure : creating macros for critical situations 

 Thanks notepad++ to exists and to be really FREE !!

Maybe the "compare two documents" feature is currently missing ? I will search…

Browse on the official site : http://notepad-plus.sourceforge.net

Obviously, my second friend is Paint.NET for image editing…also thanks to him.

Le Framework.NET SDK contient des outils bien connus tels que GACUTIL.EXE ou SN.EXE…
Parmi ceux-ci un outil peut trouver sa place dans des projets .NET notamment lorsque l’on souhaite "industrialiser" une assembly pour :

• connaitre ses dépendances
• tracer sa logique de chargement des bibliothèques liées
• controler que les versions d’assemblies chargées sont les bonnes
• comprendre une erreur de chargement d’une assembly dépendente

Cet outil se nomme Assembly Binding Log Viewer et se trouve notamment dans le Framework SDK depuis : C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\fuslogvw.exe

L’application se présente de la manière suivante :

et pour activer les traces complètes, il faut créer si nécessaire les valeurs suivantes dans la base de registre et passer leur valeur DWORD à 1 :

HKLM\Software\Microsoft\Fusion\LogResourceBinds
HKLM\Software\Microsoft\Fusion\ForceLog

Bien entendu pour plus de détails : voir MSDN