Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 7 years ago.
Improve this question
I have a solution with a few projects my main project MVC a seperate project that holds all my object classes and a third that has by db classes and enity framweork stuff. When i publish the project to azure only the MVC project seems to be going up.
Im using MVC,WebApi2, EF 5, and VS2013
this is what it looks like.
So I looked at this a bit closer I think it is publishing the required DLL but in my main project im using api controllers to handle data and normal controllers to handle the views. This works fine on my machine but when published to azure it is getting "Failed to load resource: the server responded with a status of 500 (Internal Server Error)" could it be an issue with the apicontrollers and azure not playing nice?
Can you provide some more information about the other projects in your solution?
If they are just classes you are referencing, upon building the project your main solution should put a compiled .dll to reference in your MVC folder. This will get published up to Azure.
Also, how are you publishing to Azure? Are you using the built in Azure Publish tools in VS2013?
This turned out to be a reference issue where NuGet did not install entity framework correctly, and the default route was not going to the right place. To fix i ran the install command for Entity Framework again and re published.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I want to upgrade my project from angular 1 to angular 6. I have developed my application in ASP.NET MVC. I know that angular 6 is completely different from angular 1. I have searched for developing ASP.NET MVC application using angular 2 but I did not find any suitable answer. Is it possible to write and execute angular 6 (Typescript) code in visual studio?
Fair warning, upgrading an AngularJS project to Angular 6 is going to be a chore. As you mentioned, a lot of changes took place in the transition from AngularJS to Angular 2. Angular does have a guide for how to do the upgrade on their website:
https://angular.io/guide/upgrade
I would recommend following that guide to upgrade from Angularjs to Angular 2 first. Once you have that done, then I would continue upgrading in major version increments (that is what the Angular developers recommend for a large version upgrade). This site can help you with the rest of the upgrade process:
https://update.angular.io/
This probably goes with out saying, but when doing upgrades like this, version control software is your friend. Make sure you can always get back to a working version of your code.
Also, Microsoft maintains a starter template for an single page application with an angular front end and an ASP.Net MVC backend. You can spin up a copy of the template from the dotnet cli with the command:
dotnet new angular -o my-new-app
The template doesn't currently use the most recent version of angular, but It could be a good reference while going through the initial upgrade process. If you are starting a new project, you could use this template and then follow the guides above to upgrade to angular 6. Here is Microsoft's documentation on the template:
https://learn.microsoft.com/en-us/aspnet/core/client-side/spa/angular?view=aspnetcore-2.1&tabs=visual-studio
Finally, if you aren't familiar with the most recent versions of angular, I would recommend perusing the rest of the angular documentation to see what is different and how things work in the most recent version. Their documentation is really good, and it could help give you a sense of where you are headed during the upgrade process.
Hope that helps. Good luck.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I am trying to prepare the structure for a project which I know will grow in complexity. I want to use ASP.Net Core MVC for the top level navigation. Within each of the main Views I want to place an Angular 2 Application.
I have started with this Yoman template to scaffold out a starting point Angular 2 with ASP.Net Core Template. This built and ran well.
In the root of my project I want to have an AngularApps folder and within that a folder for each Angular App, say 'Scheduling', 'Utilities', 'Equipment'.
There are a couple problems I cannot understand:
How do I configure Webpack?
Do I have a single dist folder within AngularApps?
Do I have a boot-client and boot-server file for each Angular 2 application within its respective app folder?
It seems to me a pragmatic approach to plan from the beginning to have multiple Angular 2 applications, each with a more focussed responsibility. I cannot find any clear examples of how to practically make this work though. I'm sure this would be valuable for many people.
Many thanks.
We had the same issue at our company and came up with this structure.
We have one master project for ASP.NET Core, and like you... we have the root folder named apps or AngularApps in your case. We then created separate projects for each angular app we developed. Each of these Angular apps are basic node projects that we use Angular CLI to build to project. This includes Webpack and a host of other great tools for your project.
Finally, in the Production build settings, we made our output directory of these angular projects set to a specific folder in the wwwroot folder of our master ASP.NET Core Project.
I hope this helps, let me know if you have any questions.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 8 years ago.
Improve this question
In my organisation we are using Team foundation server for source control. Is it possible to use Team foundation server with Xcode?
There is no direct linkup between your XCode (Mac) and TFS (Microsoft), Both are reverse technology, But you can go through Git.
And also you can go with Eclipse and manage your repositoryy.
Team Foundation Server 2013 and Visual Studio Online have great support for Git. This automatically means that you can use TFS with all developer environments that support Git or from the command line.
Share your Xcode projects explains how you can enable Git support for use with XCode.
When you have your code in TFS, there is no problem in using the Agile project management tooling. Build is another story. You can get this working by using a cross platform build tool like Jenkins or by creating manual scripts that you integrate with a TFS build.
use git-tf or Smart-SVN for version control
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I have developed the ASP.NET application in MVC using Visual studio 2010 express edition. I have domain on Godaddy. how to deploy the MVC application on godaddy ? What steps i need to follow?
1) Publish you site on you local test machine.
2) Login to Control Panel of Go-Deddy.
3) From content select File file manager and upload you content.
4) Give proper connection string.
That's it...........
Above is high level steps.. You can check for better explanations.
It's important to note that if your app is using MVC, you will need to bin deploy it for it to work on GoDaddy. You will need to manually copy any MVC related DLLs that your project is using to your production bin directory.
Alternatively, you can set "Copy Local" equal to "true" in the Properties window for any of your MVC related project references as described in this blog post. Then when you do a Publish of your application, all of the needed assemblies will be included automatically.
Be sure to deploy the correct versions of the DLLs you need.
sure, you can deploy your MVC 4 application. Godaddy supports MVC 4. What I have done to deploy my MVC 4 application is:
1. I included DLLs such as:
System.Web.Mvc
System.Web.Routing
System.Web.Abstractions
2. I edited web.config file. I put next strings:
<system.web>
<trust level="Medium"/>
.....
</system.web>
3. Then I used the File System publish method and then I used FileZilla to transfer the files to the GoDaddy. I copied all files to httpdocs directory. You must copy just to httpdocs directory.
That's all. Good luck.
At work we have about 30 legacy sites which run from a common set of code, currently these sites are in cold fusion. For this common code we have one project, then in IIS we set up a virtual directory to include the common code into each site. This works great, as changes to core logic can be made in one place, and its replicated through all the sites. And as all of our sites are hosted on the same servers, we can also just deploy the common code and all the live sites are updated, we don't need to release every site.
However we are in the process of re-writing our sites and core code into c# and asp.net MVC 3. Its going well, except when we update the core code, we are currently copying the dlls into each site, recompiling, then releasing each site.
This is fine while we only have a couple of sites re-built with the core code, but is going to be very painful when all 30 of our sites have been re-built in .net.
Does anyone have any ideas of how to easily use and delpoy common code without having to copy the dlls to every site?
So far we've tried:
- using a virtual directory of the dlls (doesn't work as site code needs to be re-compiled, and IIS doesn't seem to like it on .net sites anyway)
- deploying our common dlls to the GAC - this is an issue as the third party libraries (eg nHibernate) aren't signed, so can't add them to the GAC too.
Thanks
Saan
The easiest way is to automate your update procedure.
But if you want to rid of copying at all then you can try thing named "codebase".
Here is description of "How the Runtime Locates Assemblies" and details of "Locating the Assembly through Codebases or Probing" http://msdn.microsoft.com/en-us/library/15hyw9x3(v=vs.71).aspx
Interesting.
I also saw in the next .net relase they have http://www.asp.net/vnext/whats-new#_Toc_perf_3 “Sharing Common Assemblies”
This will give us a couple of options to investigate thanks.