ExecuteAssembly does not work at production

  • Thread starter Egbert Nierop \(MVP for IIS\)
  • Start date
E

Egbert Nierop \(MVP for IIS\)

Hi,

In development, code below works. But at production, I'll get a assembly key
mismatch. I'm am very sure, all assemblies are compiled and copied. The
batch exec, is a .NET application as well.

Is something wrong with code below?

Thanks for your time!



AppDomain currentDomain = AppDomain.CurrentDomain;


int result = currentDomain.ExecuteAssembly(this.batchToExec, null, new
string[]{"-d", this.path, "-i", "-f", file});
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

How to send data back to dll from EXE....? 1
Dynamic Assembly Loading 2
Blow away ASP.Net temp directory upon build 3
How to use config files with .dll's (an idea - what do you think?) 3
unloading domain leaks ? 2
Loading private assemblies from a subdirectory 0
CompileAssemblyFromSource leaks handles 0
Return values get lost with Reflection.Emit 1

Top