{"id":3999,"date":"2020-04-21T12:57:37","date_gmt":"2020-04-21T19:57:37","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/odata\/?p=3999"},"modified":"2020-04-21T12:57:37","modified_gmt":"2020-04-21T19:57:37","slug":"odata-connected-service-0-9-0-release","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/odata\/odata-connected-service-0-9-0-release\/","title":{"rendered":"OData Connected Service 0.9.0 Release"},"content":{"rendered":"

OData Connected Service 0.9.0 has been released and is now available on Visual Studio Marketplace<\/span><\/span>. This release<\/span><\/span>\u00a0adds the following features<\/span><\/span> and bug fixes:<\/span><\/span><\/p>\n

    \n
  1. E<\/span><\/span>mitting service metadata to an XML file<\/span><\/span><\/li>\n
  2. E<\/span><\/span>xcluding<\/span><\/span>\u00a0some<\/span><\/span> schema types from being emitted onto the Connected Service proxy class<\/span><\/span><\/li>\n
  3. Refinements and\u00a0<\/span><\/span>minor\u00a0<\/span><\/span>bug fixes<\/span><\/span><\/li>\n<\/ol>\n

    \u00a0<\/span><\/span>You can get the extension from\u00a0<\/span><\/span>Visual Studio Marketplace<\/span><\/span><\/a><\/p>\n

      \n
    1. \n

      E<\/span><\/span>mitting service metadata to an XML file\n<\/span><\/span><\/strong><\/span><\/h2>\n

      Prior to this release, the service metadata would be emitted as a long unwieldy string in the C# or VB proxy class generated on the client.\u00a0<\/span><\/span>T<\/span><\/span>he service metadata will<\/span><\/span>\u00a0now<\/span><\/span>\u00a0be emitted to an XML file named\u00a0<\/span><\/span>Csdl.xml<\/span><\/span><\/em>\u00a0located under\u00a0<\/span><\/span>ConnectedService<\/span>\\<Service Name><\/span><\/span><\/em>\u00a0directory<\/span><\/span>. Since the service metadata is required when initializing a\u00a0<\/span><\/span>DataServiceContext<\/span><\/span><\/code>, the file is embedded in the assembly during the build process. This ensures that<\/span><\/span>\u00a0if the<\/span><\/span>\u00a0executable is moved around or packaged for distribution the file<\/span><\/span>\u00a0will be loaded<\/span><\/span>\u00a0as a manifest resource.\n<\/span><\/span>\n\"Image<\/li>\n

    2. \n

      E<\/span><\/span>xcluding\u00a0<\/span><\/span>some\u00a0<\/span><\/span>schema types from being emitted onto the Connected\u00a0<\/span><\/span>Service<\/span><\/span><\/span>\u00a0proxy class<\/span>\n<\/span><\/span><\/strong><\/strong><\/h2>\n

      \"Image<\/li>\n

    3. \n

      Refinements and minor bug fixes<\/strong><\/strong><\/span><\/h2>\n
        \n
      • A bug was observed when updating Connected Service without visiting all wizard pages. For the wizard pages not visited, the choices and values entered when the Connected Service was initially added would be replaced with defaults.<\/li>\n
      • For users who elected to generate multiple files when adding a Connected Service, later when updating the service proxy they’d get multiple prompts confirming if they wanted to replace the existing files. In some instances, the prompts would fill the screen and cause the extension to crash.<\/li>\n
      • A few navigation and naming refinements also made it into the release<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n

         <\/p>\n

         <\/p>\n

         <\/p>\n","protected":false},"excerpt":{"rendered":"

        OData Connected Service 0.9.0 has been released and is now available on Visual Studio Marketplace. This release\u00a0adds the following features and bug fixes: Emitting service metadata to an XML file Excluding\u00a0some schema types from being emitted onto the Connected Service proxy class Refinements and\u00a0minor\u00a0bug fixes \u00a0You can get the extension from\u00a0Visual Studio Marketplace Emitting service […]<\/p>\n","protected":false},"author":25333,"featured_media":3253,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3999","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-odata"],"acf":[],"blog_post_summary":"

        OData Connected Service 0.9.0 has been released and is now available on Visual Studio Marketplace. This release\u00a0adds the following features and bug fixes: Emitting service metadata to an XML file Excluding\u00a0some schema types from being emitted onto the Connected Service proxy class Refinements and\u00a0minor\u00a0bug fixes \u00a0You can get the extension from\u00a0Visual Studio Marketplace Emitting service […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/posts\/3999","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/users\/25333"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/comments?post=3999"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/posts\/3999\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/media\/3253"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/media?parent=3999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/categories?post=3999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/odata\/wp-json\/wp\/v2\/tags?post=3999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

      4. Support for excluding operation imports was introduced in 0.7.0<\/a> release. The idea behind that feature was to help you control the size of the generated proxy. In this release, we have enhanced that to support exclusion of schema types – enum, complex and entity types. The user is able to deselect schema types that they do not wish to have emitted on the Connected Service proxy. However, to guarantee that the auto-generated code always builds, if a user deselects a schema type that another selected schema type depends on, the user will be alerted about it and the dependency included automatically. For the same reason, when a user selects a structured type, all its dependencies also get selected automatically.<\/p>\n