pako4u2k / wipflash

Automatically exported from code.google.com/p/wipflash
0 stars 0 forks source link

Attaching to existing Windows throws COM Exception "Error while unloading appdomain. (Exception from HRESULT: 0x80131015)" #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Launch the application you intend to automated manually or programaticaly.
2. Use wipflash to attach to an existing instance
3. Carry out automation testing as normal.
4. Wait for your test runner to unload the app domain containing your test code.

What is the expected output? What do you see instead?
No errors are expected, instead an exception is thrown unloading the app domain

What version of the product are you using? On what operating system?
Latest verion of wipflash build from sources last week, running under Windows 7 
x64 Enterprise Edition.

Note: I have attached a sample project which reproduces this exception. It uses 
the mspec test runner, although nunit has the same issue.

Appreciate any ideas or help.

Regards Ed.

Please provide any additional information below.

Original issue reported on code.google.com by ewi...@gmail.com on 12 Jul 2010 at 9:21

Attachments:

GoogleCodeExporter commented 9 years ago
Thanks Ed, will look into it. I appreciate you for providing the sample project!

Original comment by featheredwings@gmail.com on 13 Jul 2010 at 6:17

GoogleCodeExporter commented 9 years ago
Hi Ed, I've now looked into this.

MSpec raises the error for me too. However, the latest version of NUnit runs 
the same test with no problems, both from command-line and Visual Studio. I can 
also run the scenario as a stand-alone application.

Thinking about it, we used to do this on my current project with no trouble at 
all (for various reasons we use a new window each time now), so I can 
confidently say that it's not a WiPFlash problem. Annoying that MS doesn't 
provide a more useful error, though!

Please excuse me as I mark this bug "Invalid" as I do not believe it to be 
related to WiPFlash code. I suggest getting in touch with the MSpec team.

Good luck in solving it. If you do find the cause, please let me know and I'll 
update this bug with the details.

Original comment by featheredwings@gmail.com on 22 Jul 2010 at 9:37