So, I have a solution that's scoped to the web app. In one environment, it deploys just fine (via Visual Studio). I had originally deployed it as a farm solution in this environment, but have verified that the dll is not in the GAC and the solution (and
feature within) were fully removed. The solution appears to be deployed to a single web app (at least according to central admin). The feature in the solution shows up farm-wide, but if you try to activate it anywhere but the deployed web app, it fails. So,
question 1 - is it normal behavior for the feature to show up farm wide?
In another environment (VM w/o Visual Studio - clean snapshot that's rolled back between each test install), if I try to deploy the solution I get the error: Failed to load receiver assembly blah blah blah). This happens even if I manually copy the assembly
into the bin and restart IIS. It happens both via powershell and via central admin. Central admin accurately recognizes the solution as being web app-scoped and having a CAS policy.
Thoughts on why it can't find the assembly?
View Complete Post