New Service Fabric Stateless Web Api Core Project will not compile - azure-service-fabric

I open visual studio and do file->new project.
I select cloud->service fabric application. Then I pick Stateless ASP.NET Core. In the last window I select Web API and change the authentication to windows authentication.
When I do this and then compile the application, I get errors saying that System.Fabric, Microsoft.ServiceFabric.* are missing.
How can I get this to work?
NOTE: I have Visual Studio 2017 15.2. I downloaded and installed what I think is the most recent tools for service fabric. My "Extensions and Updates" says I have version 1.6.20170504.1.
UPDATE - This was due to the project having a dash in the name. It appears that the template cannot cope with dash casing your project name. (It had nothing to do with Windows Authentication.)

UPDATE - This was due to the project having a dash in the name. It appears that the template cannot cope with dash casing your project name.
This seems to be a problem with the template. If you don't select Windows Authentication, then it will compile fine.
In a project without windows authentication, the Nuget assemblies are:
Microsoft.ApplicationInsights.AspNetCore
Microsoft.AspNetCore
Microsoft.AspNetCore.Mvc
Microsoft.Extensions.Logging.Debug
Microsoft.ServiceFabric
Microsoft.ServiceFabric.AspNetCore.WebListener
Microsoft.ServiceFabric.Data
Microsoft.ServiceFabric.Services
When you select Windows Authentication, only the top 4 are added to the project.
If you add the four missing NuGet packages (the ones in bold above) then the project will compile just fine.

Related

ETW provider is not discovered automatically for the Service Fabric Stateless ASP.NET Core project type

I have created a "Service Fabric Application" using the "Stateless ASP.NET Core" template found in Visual Studio 2017 Pro 15.3.5. I am using using Service Fabric SDK 2.7.198.
And every time I hit F5 to deploy the sample app to my local SF cluster, the Diagnostic Events window notifies me that there are no ETW providers found in the solution. Could this be because it's a .NET core project using the new .csproj format?
Because when I create a "Service Fabric Application" using the "Stateless Service" template, the ETW providers list is automatically updated to include the provider from the sample Stateless1 app. And the stateless's app project is using the old .csproj format.
I believe this is a known issue that has been fixed in 2.8 release of Fabric SDK, which is due to be published in the Microsoft Ignite 2017 timeframe (end of September).
As a workaround you can just add the relevant provider name explicitly via Diagnostic Events window configuration.
Sorry!
I have double-checked and I have used SF tools 1.8. It was installed during my upgrade to VS 15.4. So I decided to do a clean install of VS 15.4.
I have removed my VS 15.4 installation and manually uninstalled SF SDK 2.8.211 and SF runtime 6.0.211. I have then installed VS 15.4 from scratch. And then installed SF runtime 6.0.219 and SF SDK 2.8.219 (these were the latest at the time of installation) via the Web Platform Installer. I have double-checked that I have version 1.8.20170927.3 of the SF tools installed in Visual Studio.
I reopened my existing sample projects (both Stateless ASP.NET core and Stateless) and the ETW sources were harvested automatically. I have also created a new sample Stateless ASP.NET core project and the ETW sources were also harvested automatically.
So everything works now. Thank you for your support.

MobileFirst authenticationConfig.xml 7.1 migration error on Security Access Manager sample project - how to resolve?

I'm working with IBM MobileFirst 7.1, and trying to get integration for ISAM working. So far I've been working with the sample application provided here, but I'm having issues with it when working with 7.1 MobileFirst client-side tools.
If I download and unzip the v3.5 integration package, and unzip the ISAMforMobileFirst test project, and I build it with the v7.0 CLI, it builds successfully. However, if I build it with the v7.1 CLI, I get an error like this:
Migrating project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630.
[Error:
BUILD FAILED
/Applications/IBM/MobileFirst-CLI-7.1/mobilefirst-cli/node_modules/generator-worklight-server/lib/build.xml:497: com.worklight.upgrader.UpgradeEngineException: FWLPL0019E: Migrating the ISAMforMobileFirst project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630 has failed because Cannot parse /Users/ferriera/Downloads/AmWorklightAdapter-3.5/sample/ISAMforMobileFirst/server/conf/authenticationConfig.xml
at com.worklight.upgrader.WLUpgradeEngine.upgradeProject(WLUpgradeEngine.java:271)
at com.worklight.upgrader.ant.UpgraderTask.execute(UpgraderTask.java:100)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
A colleague also sees this exact error in MobileFirst Studio 7.1 (in Eclipse) so I'm guessing it's not a CLI-specific error.
I would assume that support for something has changed in authenticationConfig.xml in 7.1, and this hasn't been reflected in the migrator.
A few questions:
Is ISAM integration supported in 7.1?
Whilst I realise the sample application isn't technically supported in 7.1, if/since ISAM integration is, in theory it should be feasible to make it work. What's changed in authenticationConfig.xml syntax?
Edit: looks like the failure happens due to the following: <parameter name="embedded-pki-bridge-ca-p12-file-path" value="<file-path>"/> and more specifically: <file-path>.
Change it to the actual file path, and it will not fail importing.
Nothing in the authenticationConfig.xml file is about ISAM really; it's all declarations of realms, login modules, security tests...
There is a clear failure, and a PMR should be opened.
As for a local workaround, I've attempted to remove segments in the file that I thought might trigger it, but did not succeed to find a pattern that causes it...

How to correct issue with creating Web API 2 OData Controller with Actions using EF code-gen template with VS 2013?

I have a couple of dev environments. In my older VS 2013 Ultimate, I can execute the Web API 2 OData Controller with Actions using Entity Framework template code to create classes.
The second is Visual Studio 2013 Ultimate with Update 2 RC. I can create other classes, however in trying to create the aforementioned, I get the following error:
Microsoft Visual Studio Error
There was an error running the selected code generator:
'Exception has been thrown by the target of an invocation.'
Since I have installed other components, I reset all settings through Tools / Import Export Settings / Reset All Settings.
I even completely uninstalled/re-installed - same issue on all fronts.
In both environments the code is exactly the same, connection to the same db.
I have tried using the code templates folder from the working env in the newer env - no go.
I also tried removing Update 2 RC through Windows / Installed Updates, but the request is rejected, indicating VS requires this update to run.
Suggestions?

Visual Studio Online Build access denied

I'm very new to TFS but am using Visual Studio Team Services... which i believe are largely the same configurations and technologies.
Now its possible that VS Team Services only supports web projects but they to be the only type of project that i'm able to build. I've tried several other (non-web) project types including the default console project but I always get a build error similar to one below....
C:\Users\Mark\Documents\Visual Studio 2013\Projects\App1\App1\App.config:
Access to the path 'C:\Users\Mark\Documents\Visual Studio 2013\Projects\App1\App1' is denied.
I'll get a error like the one above for every file in the project.
Can someone confirm whether Visual Studio Team Services does support building other types of projects. If so, is there some special permission or additional setting in build definition that needs to be set prior to triggering build?
Thanks. Turns out all i needed to do was to switch the build template under Build Definition->Process--> Build Process file from default to 'TfvcTemplate.12.xaml'.

What are the effects of using VS2005 to migrate from .NET 1.1

I'm working on some legacy code for a client, involving Microsoft Content Management System (MCMS).
Currently, everything is local, the code, MCMS, SQLServer, and IIS (5.x).
I copied the project folder, and then opened the new copied solution in VS2005, and let it do it's conversion thing.
But now nothing works. I've nnotice there have been some changes to IIS profile. What are the extent of these changes...??
Also, my VS2003 fails to recognize the Web Project??
Anyone have any idea what's going on?
cheers!
Not really sure the extent to which MCMS affects anything (since I have not used that tool) but as to the question on the VS2003 not recognizing the web project, the issue is that when Visual Studio 2005 does it's upgrade, it changes the format of the VS2003 project files to VS2005 format. This means that once you have upgraded a project to VS2005 you can't go back and open it using VS 2003.
As far as changes to the web project go -
VS 2005 by default completely changes the layout and mode of your web projects. If you want to retain the familiar (and IMO better) web application layout from VS 2003 you need to use the web application project option which is available as a download - details are here
Hope this helps.