Quantcast
Channel: All Forums
Viewing all articles
Browse latest Browse all 27852

Web Deploy does not accept Xpath, problem ?

$
0
0

Hi,

I'm exporting a web application using web deploy 3 , for MS Petshop Application , the web.config file contains the following SQL connections:

<connectionStrings>

<!--

SQL connection string for Profile database --><add name="SQLProfileConnString" connectionString="server=(local)\sqlexpress;user id=mspetshop;password=pass@word1;database=MSPetShop4Profile;min pool size=4;max pool size=4;packet size=3072" providerName="System.Data.SqlClient"/>

<!--

SQL connection string for Membership database --><add name="SQLMembershipConnString" connectionString="server=(local)\sqlexpress;user id=mspetshop;password=pass@word1;database=MSPetShop4Services;min pool size=4;max pool size=4;packet size=3072" providerName="System.Data.SqlClient"/>

</connectionStrings>

when I export the site , and using parameter entry for XML config file with match string '//connectionStrings/add[@name='SQLProfileConnString']/@connectionString'  I get the below error during site import:

[10/30/2012 2:43:46 PM] Parameter entry 'SW/1' is applicable to 'Default Web Site/SHOP2\Web.config' because of its scope.

[10/30/2012 2:43:46 PM] Parameter entry 'SW/1' could not be applied to 'Default Web Site/SHOP2\Web.config'. Deployment will continue with the original data. Details:

No matches were found for the search string '//connectionStrings/add[@name='SQLProfileConnString']/@connectionString' (type 'XmlFile').

[10/30/2012 2:43:46 PM] Source filePath (Default Web Site/SHOP2\Web.config) replaced with changed attributes (parameters) because of rule Parameterization.

[10/30/2012 2:43:46 PM] Adding file (test/SHOP2\Web.config).

----------------------------

any ideas about this is happing , the Xpath I'm using looks to be correct , but webdeploy doesn't seem to understand it ?


Viewing all articles
Browse latest Browse all 27852

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>