You were correct, it was much simpler to simply deploy it from VS2012 than manually swapping out the DLLs. I do have on more question, when I attempt to run with the debugger attached, once the FBAManagement features have been activated I get a Visual
Studio error stating "Object reference not set to an instance of object". This isn't an error within the FBA module, but an error within Visual Studio itself.
Clicking OK simply closes the dialog, but the debugger never attaches. The solution is still deployed successfully as well. Seems the debugger fails to attach due to the above error, but I am not sure what exactly it is referencing. Manually attaching to the
w3wp process allow me to set breakpoints that turn red, but they are never hit when activating various functions within the FBA pack.