Home → Problems →

appveyor.pubxml

• Edit

emanuel.lundman

23 Sep, 2014 09:19 AM

Having trouble building when Package for webdeploy is checked.
Getting: "The value for PublishProfile is set to 'appveyor', expected to find the file at 'C:\projects\[PATH]\My Project\PublishProfiles\appveyor.pubxml' but it could not be found." (replaced project name/path with [PATH] in the example above).
Build succeeds if it's not checked.
Any ideas on how to get it to build and package a webdeploy package to be used by your deploy agent later on?
It's an asp.net site and from what I could gather from the documenation it should work to only check the box and get the artifacts automatically (for later use and deploy by your agent). Am I doing wrong?
Also, where am I supposed to specify sitename and ports etc when deploying using your agent software? Is it possible to specify somewhere directly in the appveyor gui, or do I have to create a config file?

1. Support Staff 1 Posted by Feodor Fitsner on 23 Sep, 2014 04:58 PM

   

   I guess that project is "Website" (without *.csproj or *.vbproj), not a regular Web Application Project (WAP). Currently, AppVeyor doesn't support automatic packaging of Website project, so this is something we could add in the future releases.

   • Edit

2. 2 Posted by emanuel.lundman on 23 Sep, 2014 07:24 PM

   

   Actually. It's not. It's an old vb application and has been a website but
   it's been upgraded some time ago and it's got a vbproj file. I switched to
   script just to try it out and added my own pubxml file and got it working
   after a while. But it should work without all that. And would be glad if we
   could make it work. :/
   Any other ideas on what could be the problem?

   23 sep 2014 kl. 18:58 skrev Feodor Fitsner <
   [email blocked]>:

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 23 Sep, 2014 07:40 PM

   

   Is it a public project?

   • Edit

4. 4 Posted by emanuel.lundman on 23 Sep, 2014 07:48 PM

   

   No. Private GitHub.
   Any info I can give you without making it public?
   Maybe a path issue? But I guess in that case someone else should have had
   the same issue already. :/

   23 sep 2014 kl. 21:40 skrev Feodor Fitsner <
   [email blocked]>:

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 23 Sep, 2014 07:59 PM

   

   Sure, I will give it thought and let you know.

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 23 Sep, 2014 10:13 PM

   

   Gotcha! VB explains everything. For VB projects publishing profile should be saved to a different location <project_root>\My Project\PublishProfiles rather than <project_root>\Properties\PublishProfiles as for C#.

   I'm going to fix that and publish update later today.

   • Edit

7. 7 Posted by emanuel.lundman on 23 Sep, 2014 11:19 PM

   

   Great! Thanks!

   Best regards,
   Emanuel Lundman

   From: Feodor Fitsner <[email blocked]>
   Reply: Feodor Fitsner <[email blocked]>>

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 24 Sep, 2014 06:20 AM

   

   Update with VB WAP packaging support has been deployed. Let me know how it works for you.

   • Edit

9. 9 Posted by emanuel.lundman on 25 Sep, 2014 11:30 AM

   

   Thanks, got it working! :)

   • Edit

10. emanuel.lundman closed this discussion on 25 Sep, 2014 11:30 AM.