Last week B&R Business Solutions won a contract for a SharePoint and FBA installation and that got me on the kick of FBA again. Last weekend I built some code to retrieve the username for a FBA user and during that process I ended up wanting to debug my browser based InfoPath 2007 form. This was going to be the first time for me to try this because in the past I've always made my forms code free because I never wanted any of my clients to maintain code for InfoPath 2007 form if it could all be built in Visual Studio Web Service or Class project. My thought was it should be extremely easy to do because I had a Visual Studio 2008 VSTO InfoPath 2007 project and the form was web based. I was hoping debugging was going to be as easy as SharePoint debugging is and believe it or not it was. To debug my web based form all I had to do was attach the w3wp.exe process where my InfoPath 2007 web based form was running under to my Visual Studio 2008 VSTO InfoPath 2007 project and set my break point in the code. I was really surprised it was this easy to do because I was guessing that there had to be something funky to make it work but I was totally wrong.

Since I'm doing this extra SharePoint/FBA project with Nas, I only suspect that I will do more things with InfoPath and FBA. Most likely I will end up building a new .NET Class for retrieving FBA user information based off user id for pre-populating web based InfoPath 2007 forms.

Well it's time for me to get some sleep because I've a lot of things to do tomorrow. I hope everybody has a great weekend.

Cheers,
Michael

That's right it's time for the South Florida Code Camp and I'll be down there giving a new session on InfoPath 2007 and Visual Studio 2008.  For this session I'm thinking about changing a couple of things around and doing some really new stuff that includes C# code for updating AD and XMLFormView control for displaying an InfoPath 2007 form.  I'm thinking that the InfoPath 2007 form will be a data entry form that allows users to update their AD information.  I've been thinking about this new presentation for a while and since Visual Studio 2008 was officially released I figured that I should also change up the InfoPath part.  I'm really excited about building the new code and presenting it and after the code camp is over I'll post it on my Code Camp and User Group page.

All the information about the South Florida Code Camp can be found on the http://codecamp08.fladotnet.com/ website.  From what I heard while at Philly Code Camp from other speakers this code camp is suppose to be as big as or bigger than the Philly Code Camp one.  To see what sessions are currently on tap checkout the agenda page http://codecamp08.fladotnet.com/agenda.aspx.  The code camp is going to have 12 different tracks and that means tons of sessions.  The "SharePoint/ Office" track already has my "InfoPath 2007 and Visual Studio 2008" session and "Utilizing Visual Studio 2008 capabilities for better SharePoint Development Part 1 and Part 2" sessions on tap.  In my opinion this track is already shaping up to be a killer track.

I'm really excited about this code camp and I'm glad to have the chance to speak at it and I hope to meet some new SharePoint colleagues there to.  Well I'm about all posted out for the night.  Hope to see some of you there.

Cheers

On Saturday when I was adding my finishing touches to my demo for the Philly Code Camp I ran into an error with Visual Studio 2008 VSTO and InfoPath 2007. Whenever I tried to run my InfoPath 2007 form in debug mode I got the following error.

"Microsoft Office InfoPath does not recognize some or all of the command line options. Exit and restart Microsoft Office InfoPath with the correct command line options"

When I discovered this error and found out that it happened with a brand new project my heart started to beat a little faster (ok lot faster) because I knew the pressure was on to fix the problem before my session started. I started to do searches on the internet and I couldn't find any answers and then I did one final search and I found some link that talked about a similar error with Visual Studio 2008 Beta 2 and another office application. It mentioned about updating Office 2007 with a patch to fix the error. After reading that I looked at the version I was running and notice that I wasn't running SP1 for Office 2007 and decided to install that and see if it would fix the error. Luckily I had internet access at the code camp and started the download and about 30 minutes later I got it downloaded and installed. Then I crossed all my fingers and toes and tried the debug mode again and it worked. By installing SP1 for Office 2007 fixed the problem. I'm sure there will be many more little things pop-up and if I run into them I'll be sure to post them.

By the way Philly code camp rocked the house and I'm glad that I got a chance to speak.