"Error 104 Method 'Private Sub snpccore_BeforeDelete(e As MicroFour.StrataFrame.Business.BeforeDeleteEventArgs)' cannot handle Event 'Public Event BeforeDelete(e As MicroFour.StrataFrame.Business.BeforeDeleteEventArgs)' because they do not have the same signature. C:\projects\MetSYSDotNet\MetSYSDotNet\App_Code\MetSYSSnapShotBasePage.vb 165 121 C:\...\MetSYSDotNet\"

I get the same error showing in the editor for each line as well.  I'm not sure why it thinks that the signature is not the same since it clearly is since it's clearly working (the event is getting called and it's properly calling the method I've set up with the object reference and such so I can parse and log all the data changes and they are indeed being logged properly). 

As I said, the build succeeds, unless there is ANOTHER error, in which case it's really painful to find the real error in all the other stuff.  I'm also getting the same issue with the BeforeDelete event which I'm using the log deletes as well, but I figure it's going to be the same issue.

BTW this is with version 1.6 and upgrading to the latest version isn't a option for a few days as the boss wants to get this version out the door in about 4 days.  Obviously this isn't going to be a stopper since it's working, but if there's an easy fix it's going to make any other troubleshooting easier for me.  I'll be ok with finding out that the latest version woudl make this go away since I'll be moving to it soon, but needed to ask anyways.

Hi Cyrus,

Based on the error it is clear that you have an assembly version problem.  I don't do web development yet, but the current beta version 1.6.5.1 is pretty stable and you may want to try that, and if that does not work, you could go back to the previous version and that may clear the issue since in some of your folder there should be a different assembly with the different signature.

So make a backup of your project and upgrade to the latest version which will require you to do a clean install of SF anyway.

I don't see how there could be an assembly version problem since it's setup in the recommended fashion where the business object assembly builds when the web project is built.  As I mentioned, as this point in the release cycle, and based on the fact that it actually compiles and runs just fine despite the ghost errors, upgrading is not an option until I get this out.  Then the FIRST step is to upgrade to 1.6.5 right away as I start to work on the .1 release of the product.  At this point it just means that I have to comment out ALL my logging code if I create an actual error so I can find it, unless of course the error is in the logging code, but I'm finished with it now and it's working so I'm not going to be touching it again until at least the .1 release.