There are some entities that are supported in V2 that are not yet supported in V3. Is there any guidance on how to use both V2 and V3 in the same app?
A hybrid model for v2 and v3 is not supported as the assembly names might conflict in the same project. You can use 2 different projects in same namespace to access v2 and v3 separately.
Related
Is there a generator to convert OpenAPI 3.0 to Swagger 2.0?
Mashery, an API gateway, requires Swagger 2.0 format on input to open endpoint.
LucyBot api-spec-converter (online version, GitHub repo, Node.js module) can convert from OpenAPI 3.0 to 2.0.
API Transformer (paid service) also claims to be able to convert OpenAPI 3.0 back to OpenAPI 2.0. It has a command-line version too.
Keep in mind that OAS3→OAS2 convertion is lossy in general, because OAS3 has features that did not exist in OAS2 (such as multiple servers, oneOf/anyOf, different schemas per media type, objects in query string parameters, cookie parameters, and others).
I needed version 2.0 for Power Automate.
When you are building some Azure Functions, try to create them in Visual Studio and enable any checkbox that is named Swagger not OpenAPI.
Now the API of your Azure Function contains the swagger.json that you can set into Power Automate Custom Connector.
In the picture below we can see in the year 2018 in VS2017 there is no Stateless Web API template in Service Fabric templates in VS. Why was this removed and what are it's replacements?
Because at the time you took the first screenshot, probably using .NET SDK 2.8 or earlier and SF tools for VS 1.7 and earlier, Service Fabric and the WebApi templates were based on dot net framework only.
The releases that came after Service Fabric .NET SDK 3.0 and SF tools for VS 2.0 , like the one in the screenshot, started a migration to .net standard 2, now you can target dot net framework or dot net core using the same libraries targeting .Net Standard. For A while you had both templates available, now everything is based on core.
The main difference between the old and the new is that the previous templates you used dot net framework 4.6.2 + Owin, now you use AspNet Core with any framework compatible with the .Net Standard 2.
You might get more info from these release notes:
https://blogs.msdn.microsoft.com/azureservicefabric/2017/09/25/service-fabric-6-0-release/
https://blogs.msdn.microsoft.com/azureservicefabric/2018/01/26/service-fabric-6-1-release/
The samples I've found so far use either
repository.FindPackage()
or
repository.GetUpdates()
But both a v2 of the NuGet .NET API. Where can I find an example of equivalent for v3?
We are planning to upgrade our app from V2 to V3. I have read all the documents but there is nothing specific saying the issues of moving V2 to V3. V3 is REST based and V2 was based on QBXML so anything specific you want developers to note for upgrading the code to support V3? Also any upgrade tool would be awesome that can replace V2 to V3 would be very helpful to developers.
You can refer the following docs -
https://developer.intuit.com/docs/0025_quickbooksapi
https://developer.intuit.com/docs/#api/deki/files/1463/gettingstartedwithquickbooks.pdf
JAVA/C#/PHP devkits and usage details are available here -
https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits
PN - V2 and V3 both are REST based APIs.
If you have any entity specific qts then you can post it in IPP's live community.
https://intuitpartnerplatform.lc.intuit.com/
Thanks
According to the following URL, there are three versions of the Entity Framework Storage Schema Definition Language:
http://msdn.microsoft.com/en-us/data/jj652016.aspx
I am developing a tool that should support all of them (including the legacy versions), but unfortunately I was not able find a document that describes the differences between them.
Does anyone know such document or able to describe the differences?
There are 3 main versions of EF artifacts (i.e. CSDL, SSDL and MSL). V1 was introduced in the first version of Entity Framework shipped as part of .NET Framework 3.5 SP1. V2 was introduced in EF4 shipped with .NET Framework 4. V3 was introduced in EF5 shipped with .NET Framework 4.5. V3 will also be used by EF6 that will not be shipped as part of .NET Framework but will be a standalone release - here is the project site http://entityframework.codeplex.com. Changes to artifacts (and therefore increasing the versions) are necessary when new features are added to the Entity Framework and it's not possible to use the existing versions to implement these features. I don't have a list of what changed between V1 and V2 but you can find the list of changes between v2 and v3 here: http://msdn.microsoft.com/en-us/data/jj650889. One way to find what changed is to compare schemas for v1 artifacts with corresponding schemas for v2 artifacts. You can find the schemas in System.Data.Entity.dll - they are embedded resources or on the http://entityframework.codeplex.com by browsing the EF6 code (under src/EntityFramework/Resources/System/Data/{EntityModel|MappingSpecification}) - the schemas have not changed since EF5.