InfoPath Dev

Hi everyone!

Is anyone having more success than me trying to use Visual Studio 2012 with InfoPath 2013? - I have made completely clean installations of IP 2013, VSTA 2012 and Visual Studio 2012, all of them the RTM versions.

 

When I open IP, then open a code window,  add in a Reference (eg System.Windows.forms), do some coding, test the form, and everything works well.

But as soon as I close Infopath, re-open the form, and then go into the Code window, all my references and "using..." statements have been lost, but the actual code I typed is still there..

 I've verified this on 2 different PCs, with the same result.

I've read other posts where people are losing the .NET target version when they re-open their code, but my case is worse, having to recreate the the References each time.

 I'm fairly sure this is an issue with either VSTA2012 or VS2012 - but wonder, is anyone experiencing the same problem, or any workaround known?

I will also try and report this to Microsoft, and will post their response here, but if any questions/suggestions or workarounds, I would be delighted to hear from anyone.

 

thanks and regards

David

 

It isn't you! It is me as well, at least with System.Windows.Forms (oh, and setting the target version of .NET - that always defaults back to 2.0 for IP 2010 forms). It seems to me that this is an issue with the project defaults - in IP 2010 & 2007, if you had a filler form and added code, the ref to System.Windows.Forms would already be there - now, you have to add it and you have to add it again every time you open the darn thing. If I come across a work around, I'll post back to this thread.

I should add - I don't seem to be losing my using statement for System.Windows.Forms - just the reference - so that does sound like a difference between our two situations.

 Hi Hilary,

If you add a reference to something else, or a Service reference? does that not get lost on your PC?

(maybe if it's only windows.system.forms it's not so bad, and I can live with that...)

 

Given that a few people have reported losing their target framework, does this sound like a bug in VSTA2012, or somewhere else?

 

PS - A few times in the past your posts have been really helpful, so thanks for all your posts :-)

A quick follow-up on this...

The problem seems to be limited to WINDOWS.SYSTEMS.FORMS, other references do get preserved OK.

(unluckily for me, I only tested with Windows.systems.forms and assumed that other references would be the same)

 So I'll just do my screen messages another way, and I should be able to live with this.

 

regards

David

I am not sure where the bug is (VS or IP) but it just appears that some settings are put back to the default every single time you open the project. It is one of those things I sort of expect an update to come along at some point and fix.

I have a similar and even MORE destructive issue. When I close my form, I can't get back in to the code. I get "The filename directory name or volume label syntax is incorrect". While in code view if I look at the properties it appears the code path is in my temporary internet files path, which of course will be destroyed when the app closes. I may submit a but to MSFT support as this makes my dev environment unusable.

I submitted a MSFT Incident 113050510415587

 Thanks - let us know what you learn. I've seen that my code sometimes gets saved to a temp file, but on close seems to write to the selected location - but hadn't tracked through that since most of my IP 2013 stuff at this point has been quick testing for bugs in existing forms.

It may have to do with a form that was started in IP2010, then moved to IP2013. My tests in a IP2013 only form don't have the problem.

Related thread http://social.msdn.microsoft.com/Forums/en-US/sharepointcustomization/thread/b084d947-ef30-43a0-b49c-1fd04a32417f/