General

Re: Publishing to a web server with a relative URL

Gennady Vanin (Геннадий Ванин, Новосибирск) — Sun, 12 Aug 2012 18:09:52 GMT

How do I archive Infopath forms uploaded into Sharepoint 2007 when my Sharepoint site runs low on storage?

Update:

Oops, really I would like to know how develop Infopath forms in scalable manner,
i.e. in a manner that they can be more easily moved/copied to another location (Sharepoint site or whatever),
considering that

publishing/connection location are hard coded by Infopath Publishing and connection wizards
Infopath templates of type/compatibility Sharepoint List Form and Workflow as well as Main Data Connection/Source are unmodifiable
and data connection files cannot be generated from or daved to in these types of forms
etc,

Re: Publishing to a web server with a relative URL

Hilary Stoupa — Sun, 12 Aug 2012 12:39:32 GMT

Well, like I said, it is an old post. I'm not familiar with the product that was mentioned, I assume the name was "XSN Deployment Tool" based on the previous posts. I also assume it is a product we no longer have a available. Is there something specific you are trying to learn by resurrecting a 6 year old post?

Re: Publishing to a web server with a relative URL

Gennady Vanin (Геннадий Ванин, Новосибирск) — Sat, 11 Aug 2012 14:44:12 GMT

Hilary Stoupa:
Hmm, yes, given the post is from 2006, the link may be to a tool we no longer have available. I'm wondering with content types if it would even be compelling any longer. Here's a link to our current products page.

This webpage (and some around) do not mention migration tool(s)....

Probably some products there include the migration functions, but I am not expert in them.
Could the name of product be mentioned explicitly?

Or migration tool's web page is rather here?

Re: Publishing to a web server with a relative URL

Hilary Stoupa — Fri, 10 Aug 2012 17:22:29 GMT

Hmm, yes, given the post is from 2006, the link may be to a tool we no longer have available. I'm wondering with content types if it would even be compelling any longer. Here's a link to our current products page.

Re: Publishing to a web server with a relative URL

Gennady Vanin (Геннадий Ванин, Новосибирск) — Fri, 10 Aug 2012 14:56:56 GMT

shailaja:
Hello leondns,
Link for XSN Deployment tool ishttp://www.infopathdev.com/webstore/detail.aspx?itemid=21

Hope this helps!

This link is broken.

What are XSN deployment tools?

Re: Publishing to a web server with a relative URL

leonbns — Tue, 30 May 2006 11:28:26 GMT

Thanks

Re: Publishing to a web server with a relative URL

shailaja — Mon, 29 May 2006 11:19:41 GMT

Hello leondns,
Link for XSN Deployment tool ishttp://www.infopathdev.com/webstore/detail.aspx?itemid=21

Hope this helps!

Re: Publishing to a web server with a relative URL

leonbns — Mon, 29 May 2006 11:04:54 GMT

Patrick, where can I find this XSN Deployment tool?

Re: Publishing to a web server with a relative URL

Patrick Halstead — Sat, 08 Apr 2006 07:06:27 GMT

Hi Silverscubie,
There is a trick here. You don't have to enter the second value. :) But, that's not what you want I think. You need our XSN Deployment Tool to deploy to multiple SharePoint sites programmatically (for example, via a build script) - check out our products page. Microsoft is improving SharePoint deployment significantly 2007 with Site Collections, but that probably does you no good since you're publishing to a Web server.

Publishing to a web server with a relative URL

silverscubie — Fri, 07 Apr 2006 17:36:11 GMT

Hello,

Has anyone tried to publish a form template to a web server using a relative URL? When I try to publish a info path template, I select "Publish to a Web Server". I then type in the fully qualified URL to the server, and when again prompted for the URL for users to access the form, I must type in a fully qualified URL again.

For example, I must type in "http://servername/forms/template.xsn" or "http://www.blah.com/forms/template.xsn". I'd prefer to type in "forms/template.xsn". Why would I want to do that? Well, if I type in the first way, then the servername must be recognized in either a client's host file or be on the same network where the DNS recognizes it. For the second method, what if there were two sites on the same machine but I wanted to share the same form template? Why publish it twice if the physical location is the same?

Does this make any sense?