So I've downnloaded the latest source code of the package actions contrib project and made some changes to the httpHandler section. Currently, it only supports the older .net 2.0 way of adding handlers to the system.web/httpHandlers section, but I also need to be able to add a handler to the system.webServer/handlers section for compatibility with the .net 3.5/4.0 web.config.
I built it, no errors, great. Then copied the PackageActionsContrib.dll to the bin folder of the website I'm using to create a new package. I create the new package, include my dll AND PackageActionsContrib.dll (I can see by the modified date that this is the version I've just built).
Then I went to another site, that does not have the PackageActionsContrib.dll anywhere in it, install the package and.. nothing. Well, the OLD action is still performed, but my additions are ignored completely. Worse yet, I've also changed the old way of adding the handler, but it is also not adding my new property (I did this just to make sure the changes were doing something at least).
Did a complete IISReset to make sure I didn't have anything cached.
Open the PackageActionsContrib.dll with .NET reflector, so you're absolutely 100% certain that the code is updated in there ;-)
Right before your newly added code, add some logging so you can check if code is updated/there maybe is a problem with the code right after the logging code
Triple check if it's in the correct bin folder ( happened to me once ;-) )
Thanks guys, thanks to Richard I now know that I absolutely have the correct DLL, I added an extra property to the action ("name") and it was filled in automatically when I chose the "Add Sample" button.
And I found that I created a weird bug (that shouldn't be there), but have a workaround. Should be an easy fix, new package coming tonight!
Package actions contrib won't change
So I've downnloaded the latest source code of the package actions contrib project and made some changes to the httpHandler section. Currently, it only supports the older .net 2.0 way of adding handlers to the system.web/httpHandlers section, but I also need to be able to add a handler to the system.webServer/handlers section for compatibility with the .net 3.5/4.0 web.config.
I built it, no errors, great. Then copied the PackageActionsContrib.dll to the bin folder of the website I'm using to create a new package. I create the new package, include my dll AND PackageActionsContrib.dll (I can see by the modified date that this is the version I've just built).
Then I went to another site, that does not have the PackageActionsContrib.dll anywhere in it, install the package and.. nothing. Well, the OLD action is still performed, but my additions are ignored completely. Worse yet, I've also changed the old way of adding the handler, but it is also not adding my new property (I did this just to make sure the changes were doing something at least).
Did a complete IISReset to make sure I didn't have anything cached.
What's going on?
Some things you really have to make sure:
HI Sebastiaan,
Download the test tool from this page so you can debug your action.
Cheers,
Richard
Thanks guys, thanks to Richard I now know that I absolutely have the correct DLL, I added an extra property to the action ("name") and it was filled in automatically when I chose the "Add Sample" button.
And I found that I created a weird bug (that shouldn't be there), but have a workaround. Should be an easy fix, new package coming tonight!
is working on a reply...