maandag, januari 08, 2007

Problems starting VSTA in Infopath 2007 with Microsoft Office Server Sharepoint 2007 (.NET 3.0) installed *!!!FIXED!!!*

To fix the problem described below:

It worked for me when I did this:
uninstall .NET programmability support for .NET Framework version 2.0 and then reinstall it

(go to
Kristof his blog for full explanation)

When I want to add custom C# in an Infopath 2007 form, I get this error:

InfoPath cannot start Microsoft Visual Studio Tools for Applications.
To work with Visual Basic or C# code, Microsoft Visual Studio Tools for Applications (VSTA) is required. the Microsoft .NET Framework 2.0 and Microsoft Core XML Services 6.0 must be installed prior to installing VSTA. To install VSTA, open Add or Remove Programs, locate your 2007 Microsoft Office System installation, and then click Change

How should I make this work? Reinstalling some things? I think the .NET 3.0 will cause the problems....

This stuff is installed:

  • Microsoft .NET Compact Framework 1.0 SP3 Developer
  • Microsoft .NET Compact Framework 2.0
  • Microsoft .NET Framework 2.0
  • Microsoft .NET Framework 3.0
  • Microsoft Office Enterprise 2007
  • Microsoft Office Sharepoint Designer 2007
  • Microsoft Office Sharepoint Server 2007
  • Microsoft Visual Studio 2005 Professional Edition
  • Microsoft Visual Studio 2005 Team Explorer
  • Microsoft Visual Studio 2005 Tools for Office Runtime
  • Windows Server 2003 Service Pack 1
  • Regarding Workflow:
    Enterprise Content Management Starter Kit for 2007 Office System (beta 2 tr)
When I want to re-installing MSXML 6.0 I get this error:

Installation of MSXML 6.0 Parser failed because a higher version already exists on the machine. To proceed uninstall the higher version and then run MSXML 6.0 Parser Setup again

Kristof De Causemaeker add some more comments:
When you want to create an InfoPath Add-in project via VSTO, it also give errors...
I thinks that VSTO/VSTA in combination with .NET 3.0 and InfoPath 2007 will not work yet..... Maybe a Windows Registry problem?

2 opmerkingen:

Gabriel Lozano-Moran zei

I recommend that you download and run Registry Monitor and set the correct filters when starting to monitor. Then when you get this message stop monitoring and then look in Registry Monitor at what product code exactly is being looked for.

Kristof De Causemaeker zei

Hey Jeroen,

I found the ultimate solution.
Quite simple solution, but a very annoying problem ...

You can find the solution on my blog.