I'm looking for an Angular template for Visual Studio 2017 but I do NOT want to use the Core libraries as that requires me to rebuild all my re-usable libraries etc., and I will NEVER host my website on a non Microsoft platform (likely to put it into Azure only).
It would be nice if sign up / sign in is included.
I've tried to "convert" a core project to classic ASP .Net website with a "hack" mentioned on SO but encountered MANY issues
Any suggestions would be appreciated
Maybe you find a suitable template in the sidewaffle extension (http://sidewaffle.com/)
Related
Is it possible to utilize Umbraco with an ASP.NET Core API project?
Can these two techs work together or do I have to use .NET 4.x ?
:::::::::::::::::::::::: UPDATE ::::::::::::::::::::::::
I accepted #mortenbock's answer, but I strongly suggest to people interested in this question to also read the comments below, where #Tseng has provided some very useful answers.
Umbraco will not run on .Net Core in the current version 7.x
I believe they are working towards making it possible in version 9, which is still a long way off.
See the System requirements for Umbraco 8: IIS is still required and it will not run on ASP.NET Core
Shannon Deminick has been doing some PoC work on it: his blog post about "Umbraco CLI running on ASP.NET Core" has more details
You could use Umbraco as a headless CMS in a separate application, and then consume the content from you .Net Core application via REST or similar. At codegarden 2016 an example to use Umbraco CMS as an headless cms with custom frontend was shown
I'm looking for guidance on adding Angular (specifially the latest version of 4.0) to an existing ASP.NET WebForms project. I'm using Visual Studio 2017 and the .NET Framework version is 4.6.2.
I recently explored the official template project for Angular with ASP.NET Core but unfortunately since the dependencies, npm/NuGet packages came already set up for me I don't know how to add the proper, latest and greatest packages and extensions to an existing project. Not to mention that I'm using a completely different version of ASP.NET.
Any help is appreciated, Thanks!
UPDATE: I thought I should add more details. I specifically want to end up with Angular and at least webpack, Hot-module-replacement-middleware or some equivalent, BrowserLink, Karma + Jasmine and I want Angular to be using the latest TypeScript. This should make my question more specific I think.
Consider using the Angular CLI to build your Angular application and some editor such as VS Code that is friendly to the Angular CLI.
Consider not adding it to your Web Forms project and instead keeping it separate with its own functionality.
It can still communicate with whatever backend (Web API) you have.
I am in the middle of the development of a project.I am using asp.net framework 4.5.So far what I have developed, I have to publish it on a Linux server. So i fount that, I will have to upgrade my existing project to ASP.NET Core 1.0 in order to publish on Linux server. Can anyone please suggest me how can I achieve my goal?
You may encounter a couple of issues and looks for different solutions but a general guide can be found here: Migrating From ASP.NET MVC to ASP.NET Core MVC
For specific errors when the general migration will be done, it's worth to take a look at ASP.NET Core's GitHub page as a lot of issues that can occur during migration is described there.
I am trying to add search to an Asp.Net 5 project. The search uses the Bing Search API.
As per the instructions in the "Bing Search API – Quick Start and Code Samples" I have downloaded a file called "BingSearchContainer.cs". This file has references to System.Data.Services.Client. The file is too big to put here but can be downloaded at https://datamarket.azure.com/dataset/explore/getproxy/5ba839f1-12ce-4cce-bf57-a49d98d29a44.
I added references to System.Data.Services and System.Data.Services.Client as they were not included in the generic Asp.Net 5 (RC1) template I have used (in Visual Studio 2015) to create the site.
Although this removes the errors in the files themselves, the errors are still present in the error list and the project won't build or run.
If I hover over the using statement for System.Data.Services.Client at the top of the BingSearchContainer file it says ....DNX Core5.- Not Available.
Does anyone know how I can solve this?
You need to be aware of the platforms you're targeting. .NET Core is a new runtime, and there are no built-in libraries. Everything must be added (generally as a NuGet package), even things that were previously available from the Standard Libraries.
Check and see if the library you want is available on NuGet. If not, you'll need to find some sort of workaround or stop targeting .NET Core and just focus on the full .NET Framework.
Some workarounds
Locate a different package that does what you want and is available for both .NET Core and the full .NET Framework
Use System.Data.Services.Client on full .NET Framework and an alternative framework for .NET Core, and use compiler directives to target specific blocks of code at specific versions of the framework
Location the source for System.Data.Services.Client and try porting it to .NET Core. You should probably double check with Microsoft about this to see if they have plans to move it over already, as well as to see if there's anyone else that might help you with it
Just compile your project for .NET Framework, and don't compile for .NET Core
one thing is not clear to me that in asp.net 1.1 there was asp.net project type but from 2.0 version there is no asp.net project type option rather there is option called website type project.in website type project no link is created with IIS.why Microsoft design in this way from 2.0 version. i think there must be solid reason & advantage behind it and also tell me why no dll is created in bin folder until publish the website in version 2.0.
please explain the reason,advantage and MS Thought behind it if anyone knows the reason very well.
With ASP.NET 2.0, Microsoft split the concept into two different project types: the Website project type you're describing, and the Web Application project type. The main difference is the Website project type is designed to be folder-based, lightweight, JIT - essentially low-overhead where no overhead is justified. The Web Application project is a "traditional" project type: assembly-based, with a project-schema and optimized for precompilation.
In my experience the Website project type is unpopular with developers, perhaps for no other reason than it is different from almost every other project type. The limitations should theoretically make quick-and-dirty website projects more agile, but frankly I don't find the overhead of a Web Application project a concern.
MSDN covers the differences between the two here: http://msdn.microsoft.com/en-us/library/aa730880%28VS.80%29.aspx#wapp_topic5
Because they forgot to add the template. That bug was rectified in SP1.
Besides, there are now two types: website + web application. Use the latter if you can, because website projects don't offer installers.