1. You can use windbg from it you can start the process.
2. You can use reflector to decompile and get the source and continue from there.

Another idea is to use process monitor to see what the process is trying to do. The fail is most probably caused by a dependency on some external thing. And process monitor can help you locate it.

1. You can use windbg from it you can start the process.
2. You can use reflector to decompile and get the source and continue from there.

Another idea is to use process monitor to see what the process is trying to do. The fail is most probably caused by a dependency on some external thing. And process monitor can help you locate it.

Update: You can use the reflector FileDisassembler add-in to create the full solution and debug it from there.

1. You can use windbg from it you can start the process.
2. You can use reflector to decompile and get the source and continue from there.

1. You can use windbg from it you can start the process.
2. You can use reflector to decompile and get the source and continue from there.

Another idea is to use process monitor to see what the process is trying to do. The fail is most probably caused by a dependency on some external thing. And process monitor can help you locate it.