There is some issue with persistance of Deployment and Debug settings.
I'm evaluating Vs.PHP 2.7.4.5932 on VS2008 SP1.
Steps to reproduce:
1) Create new 'TryVsPhp' PHP5 project via 'New project' wizard.
2) Setup some deployment and/or debug setting for Local Staging and Production configurations. Close your VS.
3) Reopen the solution - the deployment setting are still there. Close VS.
4) Copy root 'TryVsPhp' folder to a new 'TryVsPhp Copy' folder.
5) Try to open 'TryVsPhp.sln' from the 'TryVsPhp Copy' folder. As a result - all deployment/debug setting are lost.
Interesting that I haven't found any deployment setting in the both 'TryVsPhp.phpproj' files:
"General"
{
"ProjectType" = "local"
"AutoLoadTemplate" = "%s.php;class.%s.php;"
"IncludeDirs" = ""
}
"Configurations"
{
"Local|PHP 5"
{
}
"Staging|PHP 5"
{
}
"Production|PHP 5"
{
}
}
"Files"
{
"index.php"
{
"ProjRelPath" = "T"
}
}
"ProjStartupServices"
{
}
"Globals"
{
}
"References"
{
}Is this some sort of "trial" limitations, or just a bug? Thanks!
P.S. BTW the product is great! I'm definitely looking forward to purchase it.
juanc says:
The deployment and debug settings are stored in the .sou file
serik47 says:
OK, in the .sou file I've found some strings of my deployment settings. But when I copied root folder to the new location this .sou file have been copied as well. Do You have an idea why .sou file becomes unusable for Vs.Php? If You interested, I have prepared .zip files with the projects and some screen-shots as well. The scenario with moved folder is quite common when you use source control, as You known, so for me this is show stopper. Thanks!
serik47 says:
Juan, any comments?... BTW, I've got only 3 days trial left, and the described above is the only major issue with Your product I have found.
juanc says:
I found the problem. I'll get a fix ASAP.
Juan
juanc says:
Ok, I submit the change so it will show up tomorrow on http://svn.jcxsoftware.com
Here is what you need to do, the suo file stores information slightly different so if you want to copy a suo from one place to another make sure you open that solution first in the original location and close it. This will update the suo and once updated it is ready to be moved to another location.
What happened is that we used the project location as key to our settings, not we use the project name instead. That will allow to load the settings anywhere the project is located.
This change will be backported to 2.7 so it will be available in 2.8 and 2.7
serik47 says:
Thanks! Please let me know when it's done.
juanc says:
We have some issues with the build. I hope tomorrow we get a build. Fingers crossed :)
Juan
serik47 says:
I tried the build 6001 - folder rename works now. But I dot't like it anyway. This is because:
shaven says:
I am running version VS.Php 2.8 for Visual Studio 2008 version 2,8,1,6135. It is having the same issue with not updating the suo file with the deployment settings.
Stac...
juanc says:
If you reset the values, are you losing them again?
shaven says:
I tried to recreate the project from scratch using the "from file folder" method and then went in a modified the "deployment settings" then closed the project and reopened it. It wouldn't save the settings.
Stac...
juanc says:
Stacy,
I fixed the issue in the latest build:
http://svn.jcxsoftware.com
I bet your project has a long name, right? There was a problem with this...
Juan
shaven says:
sitestuff.devdcs.com
I guess it would depend on what you mean my long. I have ones that are longer that were created before this version which still work. I can try to create it with a really short name. I will let you know.
Stac...
shaven says:
Ok.. I downloaded the newest version and am still having the same issue. Also tried to name the project "sitestuff" still same problem.
However I did run into one thing I found as odd. So I created the "new project from existing folder" and setup the ftp deployment for the project. Closed the project and then immediately opened it again. The deploy option in the drop down was available. I selected it and got the error:
"This deployment type is not supported"
If you need more info let me know.
Stac...
shaven says:
I was able to get it working again by creating a new configuration type. Then I closed the app. Then I went back in and updated the original configuration type with the deployment information. Once I did this it appeared to all be working correctly. Not sure why creating a new configuration type fixed it, but somehow that took care of the issue.
Stac...
juanc says:
Deleting the suo file also could help on that.