It's been so long since I've hard coded something like that it almost hurts to build an ADODB.Command without dynamically generating the INSERT statement from the schema.
You can query them with ADO (adjust the connection string as needed):
'Requires reference to Microsoft ActiveX Data Objects #.# Library
Private Function GetHeaders(filepath As String) As String()
Dim output() As String
Dim ado As New ADODB.Connection
output = Split(vbNullString)
...
Entity is nice when you designed the database, but so few devs actually configure things like key constraints that setting up a DB first Entity is a PITA 99% of the time if you didn't develop the DB itself.
I set the parameter name to the field name. That way I can generate the command, then just set the values. I've played around with emitting a class, but that was more work than I could justify for what I typically use it for.
Yeah, I'll probably poke at it more when work slows down. We use ctree in our C++ product, and our schema changes every release. I do data conversions, so I built a version agnostic toolchain via OLEDB so I didn't have to screw around with it every major version release.
@june1992 depends which "level" you want to start to play with: there's everything from deep COM interactions and even the VBA language's formal grammar definition, to higher-level inspections - looking at the implementations of the code inspections will give you a good idea of the lower-level code's raison d'être
What is COM ? I seen that before maybe thats the part I don't get ... I know I should google COM but can anyone explain what that is ? I'm sure I'll get what this is then..
> A COM Shim is an ActiveX dll, written in C++, that acts as a native add-in, and loads the Common Language Runtime (CLR) of .NET, creates an AppDomain, and loads the .NET-based add-in. Calls to the native C++ add-in (OnConnection, OnDisconnection, etc.) are passed to the managed (.NET) add-in.
@Mat'sMug I'm guessing it can't be managed C++ either. If it's a just simple wrapper, I might be able to code something like that, but the build process would be absurd - you'd need to compile specifically for 32 and 64 bit hosts and either dynamically select at runtime or separate the assemblies by bittedness. Sounds like a supreme PITA.
I have an old computer and have visual studio 2010. It won't let me open the solution. Any ideas on how I can test this app if and once I learn some of the code and I can contribute ?
And also how can I find to fix compiler errors programmaticlly I have searched google but nothin
RD is targeting .net 4.5, not sure if VS2010 can handle it (those would be the "compiler errors", e.g. async and await keywords weren't in the language until .net 4.5)
How do I get the Rubberduck.dll file . It says its missing in my path. It says retry or set the OutputPath and AssemblyName properties appropriately to point at the correct location for the target assembly .
From the \Rubberduck-next\ReatilCoder.VBE\bin\debug\. The Rubberduck.dll is not there or its missing.
well I made a build but it came out with a couple of warnings and errors Im guessing since its not finished yet. But still gives me that warning box or message box i mean
Warning 2 Could not resolve this reference. Could not locate the assembly "Microsoft.Vbe.Interop.Forms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Rubberduck.Parsing
this is one warning . sorry there were no errors just warnings there is another though
Error 1 The type or namespace name 'Forms' does not exist in the namespace 'Microsoft.Vbe.Interop' (are you missing an assembly reference?) C:\Users\junior\Documents\Visual Studio 2013\Projects\Rubberduck-next\Rubberduck.Parsing\Symbols\DeclarationSymbolsListener.cs 3 29 Rubberduck.Parsing
You can query them with ADO (adjust the connection string as needed):
'Requires reference to Microsoft ActiveX Data Objects #.# Library
Private Function GetHeaders(filepath As String) As String()
Dim output() As String
Dim ado As New ADODB.Connection
output = Split(vbNullString)
...
VBA Rubberducking
VBA Rubberducking