We are using one third party dll(GflAx.dll) in our project(MVC 4 application) which we register to the local PC using regsvr command. How to register that dll from apphorbor while deploying project via basic git to appharbor.
Related
I'm trying to deploy an ASP.NET Core Web API into an IIS site in windows 2012 server, I've installed IIS from 0 and when I deploy the app and test a petition with Postman I get the 500.32 error.
I've already installed the .NET Core hosting bundle v 6.0.14 also I've configured the application pool to no managed code and I restarted all the services including the IIS.
Restarted the server isn't an option because I can't get physical access to the server, I'm working from a remote location
This is my dotnet --info
I'm trying to deploy an ASP.NET Core 6 Web API.
I've already done:
Compile and publish the API
Installed the is
Create a site and application to deploy the API
Paste the files from the publish folder to the site folder
Installed the netcore hosting bundle
The problem was in the compilation and publish process.
i had to add the check for Ready to run in the publish configurations, i put that and solved the issue
I'm using azure to deploy my web application, Laravel application
laravel uses site\wwwroot\public as entry point
For that reason I'm using "site\wwwroot\public" in Virtual applications and directories under application settings
Where can I find the setting of the location where the code will deploy that will arrive from VSTS (deployment source)
Application settings on Azure
Right now this is the link where whenever my project arrives from VSTS is deployed
I don't want that, I want it to be deployed in "site\wwwroot\" yet keep entry point of application same as above in bullet
Currently, my visual studio solution has 3 projects:
MVC project - to be deployed at say www.something.com
Web Api - to be deployed at api.something.com
SPA application - to be deployed at app.something.com
Will I be able to host all of these just through VSO source control? I am not sure if azure would be able to host the applications at respective sub-domains without explicitly defining them?
Can anybody please clarify? And what would be the best approach?
if you host your application on Azure App service, there is continues deployment service. You can have your code next to your site (Local Git https://azure.microsoft.com/en-us/documentation/articles/web-sites-publish-source-control/) or you can have your code in supported repository e.g github/bitbucket etc ..
And Azure App Service supports virtual directly, you can have multiple apps in the same site. see detail answer from here Publish Multiple Projects to Different Locations on Azure Website
When inspecting a dump file from our application in NTSD, I ran the !DumpDomain SOS command. I was expecting to see just the system, shared and default app domains, but in addition the was a domain called /LM/W3SVC/2/ROOT-1-130793976001194923 which had loaded quite a few assemblies.
Where does this app domain come from and what is the purpose? Our app is hosting IIS - is IIS creating this app domain?
Yes, IIS creates an AppDomain per website like
/LM/W3SVC/2/Root/Website1-x-xxxxxxx
/LM/W3SVC/2/Root/Website2-x-xxxxxxx
If one of the .NET application crashes, it will not affect the others.
From MSDN:
When a request first enters managed code (managed modules or handlers), the IIS ManagedEngine module creates an application domain. The application domain then performs necessary processing tasks, such as authenticating a user with Forms authentication or other application services provided by managed code.
I am used to creating traditional WCF services and hosting them in IIS. I do this by creating a WCF Service Application within Visual Studio.
For my next project I want to leverage the functionality found in the new WCF Web API. However I am not sure what type of project I need to create to host the service.
Nearly all the examples I have read/seen show the service hosted in a ASP.NET Empty Web Application. Is this correct? Can I not host in in a WCF Application project and add the Web API references in that from NuGet?
I did try hosting in a WCF Application but soon fell over when it came to routing and the MapServiceRoute call in the Global.asax file which gets called on Application_Start.
Any help on this would be much appreciated.
For what I gathered from the samples, you can create the WCF as you have been creating, that is, a WCF Service Application in the WEB folder of Visual Studio.