Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I went through your repro steps, except that I changed one thing -- I enabled WebDeploy for the role early, before adding the twilio+deps packs and extending a controller from TwilioController. This way, the VM was already created and the role already started. </p> <ol> <li>Publish new MVC3 role to Azure, enabling web deploy - works</li> <li>Add Twilio NuGet packs and web deploy - still works</li> <li>Extend from TwilioController and web deploy - </li> </ol> <p>The first time I did step 3, web deploy caused an error:</p> <pre><code>COM object has been separated from its underlying RCW cannot be used </code></pre> <p>I am now retrying to make sure this last step is reproducible with WebDeploy. Have removed all Twilio and am publishing again to reset webdeploy. Will update answer in about 30 minutes.</p> <p><strong>Update</strong></p> <p>Ok, this is strange. I was able to reproduce the error above. However, I closed Visual Studio, restarted, and was then able to web deploy. <a href="http://463505f37a504d24a1dd7d3d29d6afba.cloudapp.net/Third" rel="nofollow">I now have a controller in an MVC3 web role on Azure that extends TwilioController</a>. &lt;-- note this is temporary and will be removed.</p> <p>I suggest you try the steps above, and even try your repro without using WebDeploy. However, before deploying with a controller that extends TwilioController, close and restart Visual Studio. </p> <p>If that still doesn't work, try this:</p> <ol> <li>Right-click Azure project and choose Package.</li> <li>Go to portal, and click New Staging Deployment. </li> <li>Navigate to and upload the cscfg and cspkg files manually.</li> </ol> <p><strong>Final Answer</strong></p> <p>I tried the steps above. When disabling web deploy, it appears to not matter whether the package is published from Visual Studio or manually from the portal. Both keep aborting and retrying. The only way I could get the TwilioController to deploy was by using WebDeploy, but of course this is not acceptable. </p> <p>I suggest you file a support request with Microsoft. It doesn't appear to be a dependency as you mentioned though, since I was able to run the code on an instance by sneaking in the Twilio stuff over web deploy. It could have something to do with the COM object error mentioned above. </p> <p>P.S. -- you owe me 96 cents for 8 hours of a small compute instance. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload