detach disk from vm azure c#





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







3















the point is, i have to detach a disk in azure, using c# and the resourcemanager provided by azure.



atm i have following...



  var computeClient = new ComputeManagementClient(credentials) { SubscriptionId = credentials.DefaultSubscriptionId };
var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
var disk = new DataDisk(ObjVirtualMachines.StorageProfile.DataDisks.Count,
DiskCreateOptionTypes.Empty,
name,
null,
null,
null,
null,
new ManagedDiskParametersInner(resourceid, acctype));
var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines);


I didn't get it. Its primary used to attach a disk, with different parameters. There is no deattach function, so i tried, setting it to Empty. But that wont work either.



I also experimented with the disk itself. But i have to detach the disk from it, so working on the disk alone will not reach to the goal.



Any Ideas how to solve this problem ?










share|improve this question





























    3















    the point is, i have to detach a disk in azure, using c# and the resourcemanager provided by azure.



    atm i have following...



      var computeClient = new ComputeManagementClient(credentials) { SubscriptionId = credentials.DefaultSubscriptionId };
    var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
    var disk = new DataDisk(ObjVirtualMachines.StorageProfile.DataDisks.Count,
    DiskCreateOptionTypes.Empty,
    name,
    null,
    null,
    null,
    null,
    new ManagedDiskParametersInner(resourceid, acctype));
    var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines);


    I didn't get it. Its primary used to attach a disk, with different parameters. There is no deattach function, so i tried, setting it to Empty. But that wont work either.



    I also experimented with the disk itself. But i have to detach the disk from it, so working on the disk alone will not reach to the goal.



    Any Ideas how to solve this problem ?










    share|improve this question

























      3












      3








      3








      the point is, i have to detach a disk in azure, using c# and the resourcemanager provided by azure.



      atm i have following...



        var computeClient = new ComputeManagementClient(credentials) { SubscriptionId = credentials.DefaultSubscriptionId };
      var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
      var disk = new DataDisk(ObjVirtualMachines.StorageProfile.DataDisks.Count,
      DiskCreateOptionTypes.Empty,
      name,
      null,
      null,
      null,
      null,
      new ManagedDiskParametersInner(resourceid, acctype));
      var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines);


      I didn't get it. Its primary used to attach a disk, with different parameters. There is no deattach function, so i tried, setting it to Empty. But that wont work either.



      I also experimented with the disk itself. But i have to detach the disk from it, so working on the disk alone will not reach to the goal.



      Any Ideas how to solve this problem ?










      share|improve this question














      the point is, i have to detach a disk in azure, using c# and the resourcemanager provided by azure.



      atm i have following...



        var computeClient = new ComputeManagementClient(credentials) { SubscriptionId = credentials.DefaultSubscriptionId };
      var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
      var disk = new DataDisk(ObjVirtualMachines.StorageProfile.DataDisks.Count,
      DiskCreateOptionTypes.Empty,
      name,
      null,
      null,
      null,
      null,
      new ManagedDiskParametersInner(resourceid, acctype));
      var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines);


      I didn't get it. Its primary used to attach a disk, with different parameters. There is no deattach function, so i tried, setting it to Empty. But that wont work either.



      I also experimented with the disk itself. But i have to detach the disk from it, so working on the disk alone will not reach to the goal.



      Any Ideas how to solve this problem ?







      c# azure






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 14:33









      GlowhollowGlowhollow

      7510




      7510
























          1 Answer
          1






          active

          oldest

          votes


















          1














          ok, got a Solution that works...



             var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
          var disktodetach = ObjVirtualMachines.StorageProfile.DataDisks.FirstOrDefault(p => p.Name == name);
          ObjVirtualMachines.StorageProfile.DataDisks.Remove(disktodetach);
          var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines).Result;





          share|improve this answer
























          • Don't know if you know it, but you can mark your own answer as accepted, if it's the right one. It helps others to see that the question has a solution already.

            – Pedro Gaspar
            Nov 23 '18 at 10:38











          • thx, can accept tomorrow ;)

            – Glowhollow
            Nov 23 '18 at 10:45











          • Yeah, it's better to wait a little bit to see if no other answer comes! I was just making sure that you already knew it. ;-)

            – Pedro Gaspar
            Nov 23 '18 at 10:52











          • It's usually recommended that you await Async methods rather than hitting .Result (blog.stephencleary.com/2012/07/dont-block-on-async-code.html) - is there a reason you're doing it that way?

            – Rob
            Nov 23 '18 at 11:37











          • sure, we have a own automation software, wich have problems with the await. Results works better here, but you are right, await is the better option there

            – Glowhollow
            Nov 23 '18 at 12:34












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433191%2fdetach-disk-from-vm-azure-c-sharp%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          ok, got a Solution that works...



             var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
          var disktodetach = ObjVirtualMachines.StorageProfile.DataDisks.FirstOrDefault(p => p.Name == name);
          ObjVirtualMachines.StorageProfile.DataDisks.Remove(disktodetach);
          var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines).Result;





          share|improve this answer
























          • Don't know if you know it, but you can mark your own answer as accepted, if it's the right one. It helps others to see that the question has a solution already.

            – Pedro Gaspar
            Nov 23 '18 at 10:38











          • thx, can accept tomorrow ;)

            – Glowhollow
            Nov 23 '18 at 10:45











          • Yeah, it's better to wait a little bit to see if no other answer comes! I was just making sure that you already knew it. ;-)

            – Pedro Gaspar
            Nov 23 '18 at 10:52











          • It's usually recommended that you await Async methods rather than hitting .Result (blog.stephencleary.com/2012/07/dont-block-on-async-code.html) - is there a reason you're doing it that way?

            – Rob
            Nov 23 '18 at 11:37











          • sure, we have a own automation software, wich have problems with the await. Results works better here, but you are right, await is the better option there

            – Glowhollow
            Nov 23 '18 at 12:34
















          1














          ok, got a Solution that works...



             var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
          var disktodetach = ObjVirtualMachines.StorageProfile.DataDisks.FirstOrDefault(p => p.Name == name);
          ObjVirtualMachines.StorageProfile.DataDisks.Remove(disktodetach);
          var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines).Result;





          share|improve this answer
























          • Don't know if you know it, but you can mark your own answer as accepted, if it's the right one. It helps others to see that the question has a solution already.

            – Pedro Gaspar
            Nov 23 '18 at 10:38











          • thx, can accept tomorrow ;)

            – Glowhollow
            Nov 23 '18 at 10:45











          • Yeah, it's better to wait a little bit to see if no other answer comes! I was just making sure that you already knew it. ;-)

            – Pedro Gaspar
            Nov 23 '18 at 10:52











          • It's usually recommended that you await Async methods rather than hitting .Result (blog.stephencleary.com/2012/07/dont-block-on-async-code.html) - is there a reason you're doing it that way?

            – Rob
            Nov 23 '18 at 11:37











          • sure, we have a own automation software, wich have problems with the await. Results works better here, but you are right, await is the better option there

            – Glowhollow
            Nov 23 '18 at 12:34














          1












          1








          1







          ok, got a Solution that works...



             var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
          var disktodetach = ObjVirtualMachines.StorageProfile.DataDisks.FirstOrDefault(p => p.Name == name);
          ObjVirtualMachines.StorageProfile.DataDisks.Remove(disktodetach);
          var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines).Result;





          share|improve this answer













          ok, got a Solution that works...



             var ObjVirtualMachines = computeClient.VirtualMachines.GetAsync(ressgroup, virtualmname, null, new System.Threading.CancellationToken()).Result;
          var disktodetach = ObjVirtualMachines.StorageProfile.DataDisks.FirstOrDefault(p => p.Name == name);
          ObjVirtualMachines.StorageProfile.DataDisks.Remove(disktodetach);
          var newUpdateVM = computeClient.VirtualMachines.CreateOrUpdateAsync(ressgroup, virtualmname, ObjVirtualMachines).Result;






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 23 '18 at 10:32









          GlowhollowGlowhollow

          7510




          7510













          • Don't know if you know it, but you can mark your own answer as accepted, if it's the right one. It helps others to see that the question has a solution already.

            – Pedro Gaspar
            Nov 23 '18 at 10:38











          • thx, can accept tomorrow ;)

            – Glowhollow
            Nov 23 '18 at 10:45











          • Yeah, it's better to wait a little bit to see if no other answer comes! I was just making sure that you already knew it. ;-)

            – Pedro Gaspar
            Nov 23 '18 at 10:52











          • It's usually recommended that you await Async methods rather than hitting .Result (blog.stephencleary.com/2012/07/dont-block-on-async-code.html) - is there a reason you're doing it that way?

            – Rob
            Nov 23 '18 at 11:37











          • sure, we have a own automation software, wich have problems with the await. Results works better here, but you are right, await is the better option there

            – Glowhollow
            Nov 23 '18 at 12:34



















          • Don't know if you know it, but you can mark your own answer as accepted, if it's the right one. It helps others to see that the question has a solution already.

            – Pedro Gaspar
            Nov 23 '18 at 10:38











          • thx, can accept tomorrow ;)

            – Glowhollow
            Nov 23 '18 at 10:45











          • Yeah, it's better to wait a little bit to see if no other answer comes! I was just making sure that you already knew it. ;-)

            – Pedro Gaspar
            Nov 23 '18 at 10:52











          • It's usually recommended that you await Async methods rather than hitting .Result (blog.stephencleary.com/2012/07/dont-block-on-async-code.html) - is there a reason you're doing it that way?

            – Rob
            Nov 23 '18 at 11:37











          • sure, we have a own automation software, wich have problems with the await. Results works better here, but you are right, await is the better option there

            – Glowhollow
            Nov 23 '18 at 12:34

















          Don't know if you know it, but you can mark your own answer as accepted, if it's the right one. It helps others to see that the question has a solution already.

          – Pedro Gaspar
          Nov 23 '18 at 10:38





          Don't know if you know it, but you can mark your own answer as accepted, if it's the right one. It helps others to see that the question has a solution already.

          – Pedro Gaspar
          Nov 23 '18 at 10:38













          thx, can accept tomorrow ;)

          – Glowhollow
          Nov 23 '18 at 10:45





          thx, can accept tomorrow ;)

          – Glowhollow
          Nov 23 '18 at 10:45













          Yeah, it's better to wait a little bit to see if no other answer comes! I was just making sure that you already knew it. ;-)

          – Pedro Gaspar
          Nov 23 '18 at 10:52





          Yeah, it's better to wait a little bit to see if no other answer comes! I was just making sure that you already knew it. ;-)

          – Pedro Gaspar
          Nov 23 '18 at 10:52













          It's usually recommended that you await Async methods rather than hitting .Result (blog.stephencleary.com/2012/07/dont-block-on-async-code.html) - is there a reason you're doing it that way?

          – Rob
          Nov 23 '18 at 11:37





          It's usually recommended that you await Async methods rather than hitting .Result (blog.stephencleary.com/2012/07/dont-block-on-async-code.html) - is there a reason you're doing it that way?

          – Rob
          Nov 23 '18 at 11:37













          sure, we have a own automation software, wich have problems with the await. Results works better here, but you are right, await is the better option there

          – Glowhollow
          Nov 23 '18 at 12:34





          sure, we have a own automation software, wich have problems with the await. Results works better here, but you are right, await is the better option there

          – Glowhollow
          Nov 23 '18 at 12:34




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433191%2fdetach-disk-from-vm-azure-c-sharp%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Guess what letter conforming each word

          Port of Spain

          Run scheduled task as local user group (not BUILTIN)