I have created a worker service to consume my eventhub data and save that into cosmos db. But I want to deploy my worker service with my web app which is an .net core web application.
Can anyone help me out here to get my job done ?
What architecture I should follow for it?
UPDATE
Upgrade Visual Studio Enterprise 2019（Version 16.7.7） to the latest version, the problem still exists.
After my test (using Visual Studio Enterprise 2019 16.0.30406.217 D16.7), I found that when you add Existing Project as Azure Webjob to the webapp of the .net framework, it can be successful.
But I cannot add it to the webapp of .net core. I think this is a bug.
Suggestions can raise a support ticket to confirm and seek official help.
Related
I have hosted my Asp.Net Core API project on IIS on Windows Server 2016 and also installed hosting bundle for Asp.Net core apps on that; have to restart my application after few hours. Please help me to solve this.
What is the problem? Is there any error message? You need to be more specific on your issue.
I'm an asp.net developer and recently trying to archive asp.net-core.
Since it's quite new, I would like to ask, how do you launch a asp.net-core project in a Windows machine?
For normal asp.net, my approach is publishing the project using Visual Studio, bring everything to a Windows machine, use IIS to create a website and point the directory to my physical file.
How about a website that created by asp.net-core?
Do I need to install asp.net-core in server machine? (i don't prefer this)
What should I do with the published file? There are two folders generated after publishing the project:
netcoreapp1.0
PublishOutput
Well, you still can use the file system mechanism to publish an ASP.NET Core project from Visual Studio. But VS uses the dotnet CLI under the hood to do the same stuff. Usually you configure your deployment depending upon your hosting environment such as Windows Server and Linux Server.
For Windows Server
You have to install ASP.NET Core Module in order to publish on IIS successfully. This will also install .NET Core SDK. You can than have the advantages of SSL Terminations and others provided by IIS on Windows Server.
For Linux
You have to use the .NET Core SDK here as well for a published app to acquire the .NET Core runtime (This is why you get those 2 folders). You use Nginx or HAProxy to get all SSL Terminations, Port-Forwarding etc.
I have a machine with installed DNX (beta-8) and running ASP.NET 5-beta8 API Service. And what I need is to publish another one API service, that have been created using ASP.NET Core 1.0.
So I'm worried if I do not break the current old Service if I install .NET Core Tooling on this machine.
Unfortunately, I don't have an option to update old API Service to ASP.NET Core 1.0
Yes, you should be able to run dnx and dotnet side by side but it's not an officially supported scenario. The only known issue is that you cannot have VS tooling that supports both. However, if you build/publish from console, it should work.
That being said, dnx is deprecated and it will not updated in the future.
I am going to deploy my application tomorrow ,so i have few questions.I want to deploy asp.net mvc4 application on 2003 server where .net framework 4.0 is installed.My question is do i need to install asp.net mvc4 also there.Or if i copy the dll responsible for mvc in to that system is sufficient?
another question is i am using entityframework and oracle database so using ODP.NET, if this is the case do i need to install ODP.NET over there or just copying DLL system.dataaccess dll is sufficient?
Rest all i follow this two links will it work
The two links are http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx/
How to deploy MVC application in 2003 server IIS
UPDATE
today i tried and unfortunately i came to know that the framework which i was running .net 4.5 will not be supported in 2003.I made my project in to .net 4.0 and everything working fine in local system,but remote system lot of errors are coming.Method not found etc. I came to know that i have to degrade EF 5.0 to 4.4 i did it like replaced dll and changed one line begin with section but no luck as of now.I have to change somewhere else also.Do you know any proper mechanism which i need to carry forward for this?
No need to install anything explicitly except .Net 4.0. All you need is make sure that all dependencies (assemblies) of your application i.e. MVC, ODP.Net etc are present in bin directory of your application. Also make sure that ASP.Net v4.0 Web service extension is enabled in IIS.
Steps to enable web service extension.
Open IIS 6.0 Manager
Click Web Service Extensions
Enable ASP.NET 4.0
Check below screenshot.
I am planning to host the WCF services for one of my project on App Fabric. When i installed App Fabric it asked me to install the .Net Framework 4.0. I Can able to configure the WCF services written in 3.5 on App Fabric but i have to select the Asp.Net v4 as an App Pool. I feel the it using CLR 4.0 for the service.
Question is can i host my WCF 3.5 service on App Fabric as we are developing the solution in 3.5 and there is not much scope to migration to 4.0. Will is work?
The first release of Windows Server AppFabric has two parts:
AppFabric Caching Services, which can speed up access to frequently accessed information such as session data used by an ASP.NET application.
AppFabric Hosting Services, making it easier to run and manage services created with Windows Communication Foundation, especially those built using Windows Workflow Foundation.
Looks like you can not use hosting services in 3.5.
http://msdn.microsoft.com/en-us/library/ff637712.aspx
http://social.technet.microsoft.com/wiki/contents/articles/hosting-net-framework-3-x-services-in-appfabric.aspx
As far as caching goes it depends on the version, this article http://msdn.microsoft.com/en-us/library/ff381375.aspx#_Toc247686147 states:
NOTE: Beginning with the Beta2 version, the .NET framework requirements will change as follows. The Cache Service will require .NET 4.0 to be installed and Cache Clients developed using .NET 3.5 SP1 will be supported.
AppFabric only works from .net 4.0, see:
http://developers.de/blogs/damir_dobric/archive/2010/04/29/appfabric-and-net-framework-dependencies.aspx