I'm attempting to add Service Fabric Service templates in addition to the default ones such as "Stateless Service" etc. to start making services quicker.
Visual studio has export template and VSIX Project Templates options, but these templates appear only in New Project not in "add new Service Fabric Service" in a service fabric application.
The other issue is that in "add new Service Fabric Service" it automatically adds the new service to the Service Fabric Application ApplicationManifest.xml, which the other template methods don't seem to do.
After snooping around visual studio files it seems that the service fabric service templates are stored in a Visual Studio extension, however when trying to add new XML files as Service Templates and including them in manifest.xml they did not show up.
Any suggestions to how service fabric service templates could be added to VS?
Related
I have created Azure Bot service for nodeJS LUIS bot.
Downloaded the zip file to for local development.
Now I want to publish the changes back to Azure Bot from Visual studio 2017.
Which different environment variables I need to set to publish from desktop without using Visual studio services.
You can setup continuous deployment by following the guidelines in this article.
Download your source code via .zip file from the Azure Bot Service interface.
Upload your code to one of the following source control providers:
Visual Studio Team Services
OneDrive
Local Azure Git Repository
GitHub (recommended)
Bitbucket
Dropbox
External Repository
In Azure Bot Service, select "Settings", then go to the section "Continuous deployment" and click the "Configure" button under the section "Step 3: Configure continuous deployment"
In the "Deployments" blade, click the "Setup" link by the gears icon.
In the "Deployment option" blade to the right, click "Choose Source"
Select the source control service your selected in step 2 above, for example GitHub
Configure your repository-specific settings in the "Deployment option" blade, including project and branch, then click "OK"
You should see a popup notification that says "Setting up deployment source"
In the "Deployments" blade of your Bot Service, you should see a log of your current deployment.
Done!
Now when you push changes to your code repository, it will trigger an automatic redeployment of your bot's code, which you can monitor using the "Deployments" blade.
For more information, check out the complete article on Azure Continuous Deployment here:
https://learn.microsoft.com/en-us/azure/app-service/app-service-continuous-deployment
You can also open the Advanced settings in Azure:
And download the publish profile:
Then, create a new Visual Studio Node.js project using the "From Existing Node.js code" TypeScript template (selecting the folder that contains the files downloaded):
Visual Studio Node Project Wizard 1:
Visual Studio Node Project Wizard 2:
Finally, import the publish profile downloaded earlier:
You should now be able to publish directly from Visual Studio.
We are working to migrate to Azure Cloud Services (not Web Site) for our ASP.net Web Application. We are wanting to start using the Team Foundation Service with 'Continuous Integration' publishing like we currently use between AppHarbor and GitHub.
We are running into challenges when using TFS's 'Continuous Integration' feature. The builds are inconsistent when comparing Visual Studio to Azure Cloud Service to TFS to Azure Cloud Service. When we publish to Azure Cloud Service using the TFS's 'Continuous Integration', our static pages work fine but for the pages that have an *.cs extension are not able to find the controls we have placed on those pages. However, when we publish using Visual Studio 2010 to Azure Cloud Service, these pages operate correctly.
Can you offer any insight to why Team Foundation Service's Continuous Integration to Azure Cloud Service would result in pages with an *.cs extension not being able to find the controls we have placed on those pages while a build and deployment using the same exact code from Visual Studio 2010 to Azure Cloud Service works perfect?
Make sure all the referred assemblies that include the custom controls are "NOT" referred from GAC. Ideally put those in a folder (call it libs or references etc to easily identify). Then refer the assemblies from that location in your project, also don't forget to mark them Copy Local = True.
Anything that is not part of the framework should be included like this.
Tech Friends,
I could not add MSCRM 2011 WCF service reference in Visual Studio 2010. It throws error when try performing this action. How do we add this service as service reference in Visual Studio 2010 and generate all proxy classes?
Have you tried following these instrutions? Download the Endpoints Using the Dynamics CRM Developer Resources Page.
Specifically in the "Using the WSDL" section.
To add a service reference for these services to a Microsoft Visual
Studio 2010 project, you must append ?WSDL to the service URL when
specifying the address in the Add Service Reference dialog box. For
example, the discovery service WSDL address is
http://servername/xrmservices/2011/discovery.svc?wsdl.
I found the resolution for the problem and I have tested it :)
To add discovery service and organization service as reference in Visual Studio we have to add query strings: ?wsdl=wsdl0
eg:-
.api.crm4.dynamics.com/XRMServices/2011/Organization.svc?wsdl=wsdl0
The same applies for discovery service also.
Check this link:
http://social.msdn.microsoft.com/Forums/en-US/crmdevelopment/thread/033f9831-5e88-4b85-a4eb-a55985f39997
When I work with a web service in Visual Studio and I'm using a web reference, the WCF web service project is automatically started as soon as I start the client application. Interestingly, this does not change when I remove the web reference.
Is there a setting in Visual Studio to get this behaviour, without actually referencing the service? (I'm working with a WebChannelFactory.)
In the solution's properties, under Common Properties, Startup Project, you can choose Multiple startup projects and select Start as the action for both the service and the consumer.
I've been working on a process for programmatically generating Visual Studio projects using GetProjectTemplate. You provide GetProjectTemplate the name of the template (a .zip file like "MvcWebApplicationProjectTemplatev3.01.cshtml.zip") and the language ("csharp").
Here's the path to MvcWebApplicationProjectTemplatev3.01.cshtml.zip
c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplatesCache\CSharp\Web\1033\MvcWebApplicationProjectTemplatev3.01.cshtml.zip
I'm trying to find the template name for WCF Rest Service Application. It's the same template used by Visual Studio when creating a new WCF Rest Service project. I've looked all around where MvcWebApplicationProjectTemplatev3.01.cshtml.zip is saved and cannot find anything that resembles WCF Rest Service template.
Thanks Tom
The template is an extension and because of that it is not part of Visual installation (that is affected only by separately installed products). You will find the template under your user profile:
"%USERPROFILE%\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\Microsoft\WCF REST Service Template 40(CS)"