D
DavidR
Hi,
We are using Visual Studio.NET InfoPath projects in the development we are
currently working on.
We can successfully add these projects to Visual Source Safe, however if you
try to open a project after someone else has worked on it and check all files
in, you receive an error referring to the PublishUrl attribute within the
manifest.xsf file.
The PublishUrl attribute seems to refer to the users working directory. If
you then go to Visual Source Safe, check the project out, and then open the
project in Visual Studio.NET, the attribute is changed to your own working
directory behind the scenes, and the project is opened successfully.
But .. this is a pain
I'd like to be able to open the project and check
out / check in as I normally would in VS.NET.
Does someone know whether there is a fix or whether Microsoft plans to fix
this in the future?
Thanks,
David.
We are using Visual Studio.NET InfoPath projects in the development we are
currently working on.
We can successfully add these projects to Visual Source Safe, however if you
try to open a project after someone else has worked on it and check all files
in, you receive an error referring to the PublishUrl attribute within the
manifest.xsf file.
The PublishUrl attribute seems to refer to the users working directory. If
you then go to Visual Source Safe, check the project out, and then open the
project in Visual Studio.NET, the attribute is changed to your own working
directory behind the scenes, and the project is opened successfully.
But .. this is a pain
I'd like to be able to open the project and checkout / check in as I normally would in VS.NET.
Does someone know whether there is a fix or whether Microsoft plans to fix
this in the future?
Thanks,
David.