• 0

[C#] HDD died, .net reverse eng.


Question

16 answers to this question

Recommended Posts

  • 0

So my hdd died yesterday. My previous backup around 2 months old. Is there anyway to use my assemblies/debugger files generated to reverse engineer my code so I don't have to re-write everything? This whole thing has been a nightmare.

EDIT: I'm using .net 4.0 and WPF/C#.

Could use Reflector and dump it that way.

  • 0

Depending on the cause of the failure, you can try the freezer trick or using spinrite. As I said depends on the cause of the failure, imo for home users data recovery services are not feasible as they often are not the target market and often depending on how the drive has died they can be just as limited as to what they can do.

  • 0

I might point out the hard drive that failed was a pci-e revo drive setup in raid 0. But thanks for the jetbrains idea I'll look it up. Really I want the code, I can always re-construct the xaml if I need to. This whole thing has just been a nightmare. My last copy is so many thousands upon thousands of lines of code behind.

  • 0

Ok so that worked in a way (the program you gave me), however it renamed all of my variables in their own scope (I have a billion variables lol). Is there anyway to save the variable names or is that something the compiler does when converting to IL code and such?

  • 0

Ok so that worked in a way (the program you gave me), however it renamed all of my variables in their own scope (I have a billion variables lol). Is there anyway to save the variable names or is that something the compiler does when converting to IL code and such?

the variable name isnt saved when changed to ILcode, it is only saved if the member is public.

  • 0

Yeah that's what I figured. It had been a while since I studied the process of the compiler to IL code but I couldn't remember if it renamed the variables that were private or not. I think it does that for faster processing if I'm not mistaken. Oh well, either way I just started re-writing everything *sigh*. This time I will have several back ups :) I lost about 20,000 lines of code.

  • 0

Yeah that's what I figured. It had been a while since I studied the process of the compiler to IL code but I couldn't remember if it renamed the variables that were private or not. I think it does that for faster processing if I'm not mistaken. Oh well, either way I just started re-writing everything *sigh*. This time I will have several back ups :) I lost about 20,000 lines of code.

Backups are nice, but you really should be using version control. It's not just for projects with multiple developers. Bitbucket is free. Backups taken care of.

  • 0

Backups are nice, but you really should be using version control. It's not just for projects with multiple developers. Bitbucket is free. Backups taken care of.

Lol yeah I know. Pretty dumb. It wasn't ALL of my projects. Just one I had started on and just ran out of space on my back up hard drives and thought oh well this is a brand new hdd I'll back it up in a couple of weeks. Well the week before I was going to buy a new one the new hdd died lol. Lesson learned.

  • 0

1) Try software based recovery solutions.

2) Try DECOMPILER such as JustDecompile from JetBrains or Reflector from RedGate

3) Try hardware based recovery solution if the cost if worth it (Keep in mind, this method is a destructive to the disk, you will not get the original disk back).

  • 0

Have you tried harddrive recovery software such as R-Studio? It's the same software the feds use to recover deleted data.

Haha, no it's not.

Feds use encase, winhex and that other one of which the name slips me buy, fx toolkit or something.

EDIT: FTK, not tx toolkit.

  • 0

if you didn't obfuscate your code you should be able to get it completely back using a decompiler. .net Reflectoris the best, although not free. Even if some variables are renamed it's a metter of refactoring, still a lot faster than starting again from scratch.

And remember, 0 in raid-0 stands for the amount of files you can recover when a drive fails ;)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Excuse me for having an opinion, fella'... (Why am I not surprised?...) Congrats on your very informative post however...
    • By the sounds of that wall of Fox News propaganda gibberish attacking the Democratic Party you've already had plenty of "juices" flowing this morning. You've ruined what could have been a productive comment thread.
    • (Topic to get the juices flowing this Sunday morning!...) Actually, the situation has almost nothing to do with "lack of skills", especially since assembly-line skills can be taught to anyone, including Americans, certainly. Rather, the inadequacy-to-impossibility of large-scale tech manufacturing in America today, and the reasons why America finds tech manufacturing completely onerous in the 21st century, has to do with politically driven laws amid a plethora of non-scientific, utterly politicized "science-fact" that is patently false, punitive business taxation at every turn, an array of judicial fines of unimaginable scope and complexity, and, last but not least, American unionization strictures that serve to actually slay job creation and hobble all such manufacturing endeavors in America before they can get off the ground. Globalism emerged, they tell us, as the needed answer to American hubris and an unholy American drive to excel. Unless one is buried under mounds of political propaganda, it's easy to see the absurdity of labeling the employees of SpaceX, for instance, as "unskilled labor"... Etc. ad infinitum. At one time in the recent past, American manufacturing prowess was the envy of the world in a wide variety of technical fields! The current federal and state government roadblocks against America becoming competitive globally in tech manufacturing are considerable, it's true, as anyone with a working brain knows. But remarkably, that is only half the story! The other half of the story is, of course, the corporations themselves... Chinese tech manufacturing is simply unassailable in terms of profits, because the Chinese government wants to see its tech manufacturing second-to-none globally so that no companies/nations can compete in terms of ROI, and China has completely succeeded in that goal. Let's tic-off a few things: *Chinese tariff policies are set according to what is considered best for Chinese business, Chinese employees, and the Chinese people. Huge difference with how things are done with tariffs in the US--as the US government (SCOTUS in this case, Congress in others) plainly feels that tariffs are "unfair" for the limited number of citizens who may pay them, whereas nothing is "unfair" when Congress considers the Personal Income Tax rates to be infinitely hike-able, along with infinitely enlarging annual budget deficits. *The Chinese government boldly subsidizes Chinese companies to artificially amplify their profits. *The Chinese government deliberately refuses to avidly demonize Chinese businesses and does not consider Chinese businesses "the enemy", so very unlike American (D)s these days. *Chinese labor laws and businesses are allowed to set their own labor policies according to what Chinese companies consider is best for companies and their employees... Simply put, American workers in tech manufacturing are not allowed to set their own labor policies! It is the height of hypocrisy for Americans to decry working conditions in China while simultaneously ensuring that American products are manufactured in China, not in the US, simply to maximize profits. There is nothing wrong with making a profit, of course, absolutely nothing. But there is plenty wrong with attempts to normalize hypocrisy of this kind! But rank hypocrisy and the (D) party in the US are longtime bedfellows... The current government in Washington is working overtime to see if it can toss out the horribly poor, failed economic policies of the past, while the (D)s still in Washington work very hard to bring back the stupidity whenever possible. With the right policies in place, America can be an infinitely competitive manufacturer.
  • Recent Achievements

    • Conversation Starter
      jessse3334 earned a badge
      Conversation Starter
    • Reacting Well
      JuvenileDelinquent earned a badge
      Reacting Well
    • One Month Later
      Excellence2025 earned a badge
      One Month Later
    • Week One Done
      Excellence2025 earned a badge
      Week One Done
    • Week One Done
      flexorcist earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      152
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      64
  • Tell a friend

    Love Neowin? Tell a friend!