Some Minor Bugs (Descripted below) are fixed, the Search Dialog got a bit extendet, some Project Properties can get accessed and the Handling for Visual Basic Group-Files is implemented.
New Features:
Usable as Add-In
The VBSE works now as VB Add-In and as Standalone Application. When VBSE is registred as Add-In for the Visual Basic IDE, you can run it from the Add-In Toolbar or Menu and, from within VBSE create
a new Modul or use an existing Modul to copy a Procedure from the open Project (in VBSE) directly into the current VB Project. Alternatively it is possible to push a hole Module into Visual
Basic.
Visual Basic Group-Files
Now you can open Group Files as well with all included Projects listet in a Window. The posibility to open or close all Projects at ones or to open with a single click a selected one and to close or
bring it to the Top again with another single click. The Group-File get added to the Recent List, the Projects not while the Recent List stays more readable.
Project Properties:
If the File is a Project, some of the Properties can be accessed.
This is:
Exe Type
Startup
Version
References
ActiveX Objects
All Legal Info
Open Modul with Ascii Editor:
In the Dialog Preferences you can define a Ascii Editor
Search Dialog:
Now are all searches within a Session stored and reuseable from the "previous" search List. The Search is now bound with F3, to open or to serach further.
Bugfixes
Loading again Files from Property Pages, User Controls and User Documents.
Relative Paths in the Project are working now.
Sometimes the Declaration was not reading to the End.
Explorer Context-Menu missed by some VB Files (vbg, pag, dob).
In some Circumstance VBSE crashed while loading a Function/Sub.
Thanks again to all People who give me Response and Tipps. This gives me the Power to Work on.
And here are some Features, to now what you can get or to Remember what you have:
There are some build in Features in VBSE, they can be helpful, but are not present in Mind by all users .
You can Drag from the Explorer and Drop it over the VB Source Explorer to open one ore more Files.
You can Extend the Context Menue from Explorer with a Entry to open the File in VBSE. Do this in the Diaolg Options.
You can select more then one Files in the Explorer and push it to VBSE over the Context Menue. See Diaolg Preferences to control the Behavior of Copies from the Application.
You can Maintanance the Files Recent-List. Resort the Items or delete. Files who are not longer avaiable on your Disk are marked with Asterix.
You can the selected Code in the Codepane with a Click (Button in the Toolbar) copy to Window "Code Merger".
You can do this how many as you want. The Code goes at the end from the existing clipped Codes in the "Code Merger". In this Way you can put together wath you need and send it to Visual
Basic Code Window over the Clipboard.
Duplicate a Procedure into a extra Window. Usable to compare between another Procedure.
The idea for VB Source Explorer was born back in the "VB3-years".
Why I have created VB Source Explorer?
Sometimes when programming I had to write some code I knew I had already figured out in a different project or had some sample source for). Apart from VB3, not being able to launch multiple copies
of itself (which has become obsolete with VB4) I had to:
- Add the form/module that carried the code and copy the fiiting content in my project, removing the form/module from my project afterwards.
- Even worse: In case of conflicting precedure names I had to close my project, open the other project, copy the code, close the project, open my original project again, paste the code and if needed
repeat all that until I had what I needed.
I got close to mad about that.
That was when I decided to write VB Source Explorer.
Today I simply launch VB Source Explorer to look up and copy the code the easy way. Or, when working on a new project, I use VB Source Explorer to collect all the code I need and simply paste it
into my new project. Much better, easier and faster.
VB Source Explorer is:
A utility that lets you view and search VB-Sourcecode without the overhead of switching projects or launching multiple copies of Visual Basic. It's a great timesaver. VB Source Explorer prints
procedures without any special formatting. In the meantime, the last version (you will working with) has also become compatible with VB5.
This software (and all accompanying files) is provided AS IS without warranties as to performance or merchantability or any other warranties whether expressed or implied. Because of the various
hardware and software environments VB Source Explorer may be used with, no warranty or fitness for any particular purpose is offered.
Some options are not freely available to you, you will get an appropriate message about this.
To gain availability of the disabled abilities you have to:
Send me an e-mail and
- tell me what you think about VB Source Explorer.
- tell me about possible features you're missing.
- tell me about occurred errors (I implemented no extensive error-handling yet, so VBSE might unfortunately abort in case of errors).
- tell me anything you want - all your questions and suggestions.
As a "registered" user (which you will become by sending me a mail), you will have the always be informed about updates for VB Source Explorer and you'll get support via e-mail.
If you want send me some money, don't worry, I can use it.
I do spend time to programming and time is money... I miss both.
So if I get some money for my work, I can invest more time to fix bugs and implement improved functionality.
Feel free to send me whatever sum you like if you want to, it is appreciated and you help to further develop this software.
I find it very easy to work with VB Source Explorer. I hope the same applies for you. I designed the software to be self-explanatory (especially as we are talking about programmers, not exactly
newbies to computers). Anyway, some questions might arise, so let me give you a short overview over VB Source Explorer:
You can open all kinds of VB-files (frm, bas, cls, vbp, vbg and so on...) and as many files as you want or your RAM allows you to. VB Source Explorer can read files created by VB1 through VB5.
It's very easy to explore projects and search for code. In a open file you can "walk" through all the pieces of code. They are ordered by declarations, subs and functions.
You can also access the menu structure of the current form in a list window, including all parameters.
When you have found a sub or function you would like to work with, you can copy it to the merge window. You can sample as many pieces of code into the code merger as you like. When you have
collected all of your required code, copy them to your VB project. Remember that all of the code collected in the merge window will be pasted into the same module.
With the menu 'View/Options' you have the possibility to add a context menu ("Explore VB Code" by default) to the Windows Explorer. So, if you look for VB-files in the Explorer,
you have the possibility to open them using this context menu that appears when you right-click the file in the Explorer. You can also drag and drop (single or multiple) files from the Explorer over
VB Source Explorer's window to open them. If you deselect "Allow multiple instances" in the View/Preferences-menu you will a single MDI Window for every single file, otherwise each
file will be shown in a new instance's window of VB Source Explorer.
The first goal for VB Source Explorer's future is to add some more functionality to the librarian. Secondarily, an extended version of code-searching (including a filter for limitation to
special variables or objects) is planned to be implemented. The next step will then be to make VB Source Explorer an Add-In quickly and easily usable in VB's IDE.
A very nice feature might also be to search for code in any (also currently not opened) VB-files anywhere on the HDD or within a specified location. I also think about a feature to copy complete
modules or procedures, whole forms including all implied controls (or optionally only some of them), a whole menu (or a part of it), directly into the VB project file.
And some more ideas....
P.S:
Maybe VB Source Explorer will be a beta forever !?
Anyway, I will do some bugfixes and/or new features.
VB Source Explorer was written in VB5 and needs its runtime libraries.
You can find them somewhere in the Internet.
I have not yet tested all possible constellations for reading a file (remember this is a beta). Sometimes you may find a bug. Don't worry, but please do tell me about such errors so I can fix
them for a new release.
Update Avaiable
NOW Avaiable: The new
Update
