Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Oct 06, 2011 06:58 AM|LINK
I also wouldn't think that the problem has to do with version mismatches seeing as the website functions properly on my local machine, but permissions on the server (or lack of) may be a problem. I haven't configured the webapp to run under IIS on my local
machine, I'll have to try that and see if I can reproduce the problem locally.
Try it the app on your local machine is the only possibility, so you can perform various experiments changing application pool, thrust level and so on. Moreover, maybe the problem is the server itself that has a misconfigured asp.net or simply your application
pool is configured in some strong way.
About version mismatch...don't be so sure. The way .Net deal with different versions is quite complex: problems may arise just when you use structuremap due a some versioning policy or simply to the fact that you mentioned a specific version when putting
an assemply name in the structuremap configuration information...maybe normally a different dll (wkth a coherent version) is taken