Trying to follow the tutorials for IdentityServer using Visual studio 2019.
As per the instructions created a .Net Core Web Application and then an MVC project type and as per tutorials a welcome screen for IdentityServer should come at run time
But i am getting an MVC page template only like this
Is there any difference in project templates based on new visual studio updates? Or what is the correct selection of project types to get the window similar to the first image ?
It seems you are running the mvc application insteed of the identity provider service.
Go to the solution properties, Common Properties, and select Multiple startup projects. Then change the Action to Start for debug all your projects.
If you prefer start only your identity provider service set it as the Single startup project.
Related
I am creating a WPF Project with MVVM architecture. I've created the UI in one Visual Studio Project. I want to create WebAPI for the service creation for CRUD operation in a separate Visual Studio Project and I've to call the API methods in the WPF Project solution. How can I achieve it..?
I made a little app started with Databound App template. Didn't have an idea that it made use of Silverlight and at same time that this was making this framework uncompatible. I have to install Onesignal API to it for push notifications. So, I followed the documentation procedure.
It failed at 1.4 with this error when pressing OK:
Microsoft Visual Studio
A reference to a higher version or incompatible assembly cannot be added to the project
So I tried to do the same thing, in case I did something wrong, on the Blank App template which doesn't feature Silverlight and it worked.
How can either install the API in my Silverlight project or "convert" (or migrate) it to non-Silverlight?
I would like to create a Visual Studio 2012 (Premium) solution, initially containing a project for an AngularJS client. Later on, at least one ASP.NET MVC 4 project will be added defining the server the AngularJS client talks to. We would like to keep these things in one solution.
The problem is that I cannot find a fitting project template (installed or online) or a way to manually define such a project. No matter which project template I choose there is always too much cruft being added, as all project templates are based on some programming language / environment irrelevant to the AngularJS project. I would be happy with a blank project template to which only the relevant html, js, css,... files would be added.
One could of course define the ASP.NET MVC 4 project and then add the client parts to some folders in that project, we had already done such things in the past, but things get very cluttered.
Do you know how to naturally define such a web client project in VS 2012 or if VS 2013 does handle this better?
We came up with the following solution: In Visual Studio, select "Add New Web Site" -> "ASP.NET Empty Web Site". This approach fits the bill since it does not add much to our AngularJS project and hosting the application is also taken care of.
I would suggest create a new ASP.NET Web API project. File - > New Project-> ASP.NET MVC4 Web Application . In the next screen, select "Web API". Since you are doing the client only using HTML,CSS and JS , your server side becomes a bunch of APIs for which you need to create a Web API project only and not a full MVC 4 app. Even Web API project also comes with some MVC4 files and folders, which you can remove easily.
It appears that you either start a Composite C1 site by using the Visual Studio solution - or just install the exe, which contains no solution file and can just be used through the web CMS.
I need to include an MVC 4 Partial in a page on a site that was only installed with the .exe & edited only through the web CMS. Can I add a partial in the CMS (not in VS), or do I have to use VS & manually compile the site before deployment?
I have tried adding the sample MVC files from the below to my C1 site & navigating to /Home:
http://docs.composite.net/Functions/MVC/HelloWorldMVC
The URL for Composite is localhost/mysite
I try going to localhost/mysite/home - but it doesn't work.
Thanks.
do I have to use VS & manually compile the site before deployment?
Normally, you don't need Visual Studio in order to use the MVC Player - unless you have to use VS (or any other tool) to create and add views and controllers to the website. In any case, everything should work on-the-fly without having to compile the website
I am using the Lync API within a WPF application. I have used the Office365 Lync Lab 9.1 within the training kit. However when I move the code into my WPF application the PresenceIndicator or ContactList doesn't work. The controls are displayed however the status of the Lync user is not shown. I am using the exact same accounts that are working within the Office365 Training Lab 9.1.
When I add logging I am shown errors like the following for the PresenceIndicator:
Applying template...
Control 'PresenceIndicator' entering 'OnLoaded'
UCClientInitializationFailed:Failed to Create Provider. Error Type: TypeInitializationException
I am also trying the ContactList and that is outputting:
UCClientInitializationFailed:Failed to Create Provider. Error Type: TypeInitializationException
Also the InitializationError property within the InitializationCompleted event is showing an Unknown error. How would I troubleshoot this issue further?
This is a complete stab in the dark, but are you attempting to add controls to an existing WPF application that has never integrated with Lync before?
It may be that you are missing references in your app - double-check you have references to the following files in %program files%\Microsoft Lync\SDK\Assemblies\Desktop
Microsoft.Lync.Controls.dll
Microsoft.Lync.Controls.Framework.dll
Microsoft.Lync.Model.dll
Microsoft.Lync.Utilities.dll
Microsoft.Office.Uc.dll
Also worth checking:
Is your app builing against .NET Framework 3.5 or 4?
Are you building for AnyCPU?
If that doesn't help, you could try creating a new WPF application using the "Lync WPF Application" template in Visual Studio. If this works correctly, then compare this against your appplication for any differences in references, configuration etc.
This MSDN page may be useful.