I would suggest you start with a copy of the WrapperPlugin sample.
I'd be interested to know why you want to wrap a plugin? What added functionality are you planning to build?
Also check out the documentation .chm (downloads) - that has a lot of information on the inner working on VST.NET.
In short VST.NET marshals all VST calls from C++ to .NET (and back) - they end up in an object (class) called the Plugin Command Stub. That is the core level. The Framework one can use to build plugins is layered on top of that. So understand that the WrapperPlugin
sample does NOT use the Framework. As you can see in the source it implements a PluginCommandStub object - that receives the calls the Host makes to the plugin. It also implements a Host Command Stub - a similar object that receives the calls the Plugin makes
to the host.
Any functionality you wish to add, you would implement in these two Command Stub Adapter classes. Those are the points of interception.
Let me know if this works for you.