19. January 2007 18:08
The MS InfoPath team blog is currently looking for bloggers who would be interested in submitting their blog URL. All you have to do is add a comment to the following post. The below URL will take you to there post.
8. January 2007 04:38
One of my previous clients we did 2 custom InfoPath 2003 forms with Visual Studio 2003 and when we deployed and launched the forms on their machines the below error was occurring. After doing some research on the net and doing some old fashion trial by error we discovored and documented the following solution for the error.
InfoPath cannot open the selected form because of an error in the form's code.
The Microsoft .NET Framework 1.1 is not installed on your computer or the InfoPath primary interop assembly (PIA) is not registered. Use Add or Remove Programs in Control Panel to make sure that Microsoft .NET Framework 1.1 is installed or install it using Windows Update, then run Setup again to confirm that .NET Programmability Support is installed, or contact your system administrator.
Complete the following steps from the machine having the error.
· Open Control Panel – Add or Remove Programs
· From the “Add or Remove Programs” pop-up window click the Microsoft Office 2003 installation entry to highlight it.
· Click the “Click hear for support information” link directly below entry heading.
· Click the “Repair” button located on the new pop-up window.
· The Microsoft Office 2003 installation program will start the repair process (this may take several minutes before it completes).
· When finished close all the windows and then reboot the machine and then launch the InfoPath 2003 form again and the error should no longer exist.
8. January 2007 00:03
I’ve recently built a new development environment for a new InfoPath 2007 and Windows Workflow project. The installation of all the software was going really smoothly until I tried to install Visual Studio Extensions for Windows Workflow Foundation. Each time I would double click the exe to install the extensions I would get the repair and remove application for VSTO 2005 SE. I couldn’t figure out what was causing the strange interaction so I deleted the install file and downloaded it again but no luck because the same thing was happening with the new file. I rebooted the server but I still had the problem and I finally decided to move on and install the reset of the software. When I was done I deleted the all the files except for the VS 2005 Extensions for WF and I tried it again and it worked this time. Instead of installing the extensions I decided to do some more investigation on what was going on and after doing some trial and error I was able to replicate the strange interaction. The strange interaction only occurs when the VS 2005 Extensions for WF and VSTO 2005 SE installation files are in the same directory. If you remove the installation file for VSTO 2005 SE from the directory the strange interaction doesn’t occur and you are able to install the extensions successfully.
I don’t know if anyone else had or will have this strange interaction but I thought I would pass along my experience.