Skip to content

Conversation

@kcomelli
Copy link

Changed AlexaSkillsKit.Lib project to multi framework targeting library supporting .Net Framework 4.5+, .Net Standard 1.1 and .Net Standard 2.0.
Added a simple batch file and powershell to create a single multi framework targeting nuget package.
Set version to 1.7.0 (package and assembly)

Info: If you run the createPackages.cmd the NuGet package for Debug and Release configuration can be found in .\AlexaSkillsKit.Lib\bin\Packages.

I've configured some constants which may be used if you have to add some code which is only valid for a special target framework. Introduced constants are:
#NET45 ... for .Net Framework 4.5+
#NETCORE ... for .Net Core targeting (active for .Net 1.1 and 2.0)
#NETSTD11 ... for .Net Standard 1.1 only
#NETSTD20 ... for .Net Standard 2.0 only

If you edit a source file (e.g. Sdk.cs) you can easily switch the target framework using the drop--down box in the upper-left corner of your code editor window (next to the class selection drop down).

PS: I did not test it because I'm preparing an alexa backend for .net core 2.0 which is currently not active. I just did some configuration because I have experiences in creating multi framework targeting!

… of .Net 4.5, .Net Standard 1.1 and .Net Standard 2.0.

Cloned AlexaSkillsKit.SampleCore to a corresponding version for .Net Core 2.0.
Added simple powershell and batch file to create a multi-platform nuget package.
@ElvenMonky
Copy link

ElvenMonky commented Jan 26, 2018

Did you take a look to dotnetcore branch of this repository? .Net Standard 1.1 is compatible with all mentioned target frameworks, so I'm missing the point, why multitargeting is required.

Thanks for the scripts though.

@brandonh-msft
Copy link

brandonh-msft commented Apr 20, 2018

Tried pulling this branch in to an Asp.Net core Web API project and it's still wanting an HttpRequestMessage be passed to the GetResponseAsync method on the speechlet. In .Net Core these aren't HttpRequestMessage objects, they're just HttpRequest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants