Can anyone recommend a good tool for building a call hierarchy list?
I'm using VB .NET with Visual Studio Community Edition.
The Enterprise Edition has a tool available to do this, but that edition is not available to me.
The Call Hierarchy window only shows who calls you when using VB - it doesn't show who you call.
What I need to do is to select a Function or Sub and get a list of what it calls, and then what they call, and so on right down to the bottom of the hierarchy (ideally ignoring standard VB functions).
I want to pull some code out into a separate DLL but I need to know what must accompany it for it to compile and execute cleanly.
There are tools in Community edition, which can help you to do what you need:
Call Stack (runtime only)
Call Hierarchy
Find All References
Third party tools like CodeRush for Roslyn can do little more, like Debug Visualizer.
Related
We have a large chunk of legacy code in VB that I want to unit test, so step one if building interfaces. In C#, visual studio has the cool little Refactor -> Extract Interface function. VB Doesn't, though?
Is there a good way to do this in VB?
Extract Interface function. VB Doesn't, though?
Yes. Unfortunately, Microsoft Visual Studio does not support refactor functionality for VB.NET.
You can install third party tools such as ReSharper, though.
For more information, also have a look at this question on SO: Refactoring options in Visual Studio 2010 differ between C# and VB
I need to use a custom dll within my SSRS report. Please guide me how to do this in SQL Server 2008 R2 business intelligence studio.
Ok, the question is quite old, but as I had the same issue recently and as your question is not yet answered, i will give you a link that explains what to do
How to use custom assemblies or embedded code in Reporting Services
From you mail I suspect that you didn't deploy the dll on the server bin directory (and modifiy the config file).
Hope this will help you or someone else :-)
To reference a DLL, select the yellow background surrounding the report (in design view) and select Report Properties (not Report Data). Within here you have a Code section, for writing custom code and a References section to reference custom DLL's.
That said, if you want this functionality to be used by many reports, consider wrapping the SSRS reports within a c# web app. This will enable you to make use of common repeating code (like parameter passing) and reduce ongoing maintenance by code reuse.
We are in the process of creating active-x controls used within our application.
Since Microsoft stopped supporting classic Visual Basic, is it wise to use Visual Basic to develop the Active X control or the latest VC++/ATL/MFC libraries provide more feature where we can create controls faster by leaving Visual Basic flexibility?
We will not be able to use .NET/VB.NET/C# since the application is supposed to work inside containers and containers may not support latest .NET runtime.
Any other language is best fit for Active X control development other than VB and VC++?
I, personally, would recommend using Delphi for this. It is still actively developed, and has the control you get with C++, but a rapid development environment more like VB.NET.
#nobugz: If you are really interested what is ActiveX in Delphi, look at docwiki. Normally it is 100% source code (yours + VCL, VCL is also available as sources) with autogenerated COM wrappers. So all potential security problems are also in source code. If you find a security problem in VCL, please send a bug report to Quality Central.
Here is a good example on how to create ActiveX Controls with C# .NET
http://www.codeproject.com/KB/cs/CreateActiveXDotNet.aspx
By all means VB6 is the best language. After reading your question I feel that you are a VB6 developer. If you know VB6 and use it then why hesitate using it for producing ActiveX controls.
I program in Delphi as well as VB6 along with VB.NET and C# but creating ActiveX controls is the easiest in VB6 compares to all other development tools.
If you are hell bent on not using VB and if you are looking for an alternative then try out PowerBasic (commercial - very costly) or PureBasic (commercial but affordable) Get it from here or better still MinGW (a GNU C++ compiler).
I have to say that VB6 with a good book like Developing COM/ActiveX Components with VB6: A Guide to the Perplexed you will be up and running faster.
I have an ASP.NET VB.NET web project that references a VB.NET class library.
I add a new property to a class in the class library, then, from the web app, I expect to be able to use it immediately w/o errors and with full intellisense.
It used to work in 2008.
When I compile the class library, it becomes available but not until.
Was this nice feature taken away, perhaps in the interest of speed?
What's likely happening here is that the Class Library and ASP.Net applications are targeting different versions of the framework. If they are using incompatible versions of the framework then VB.Net will treat it as a file reference instead of a project reference and would give you the behavior you're seeing.
Right click on the project, select the Appilication Tab and make sure that both have the same value selected for Target Framework. That should fix the problem.
Visual Studio 2010 will officially launch on April 12, 2010. I'd say there's a good chance that problem will be fixed in it. Go see.
EDIT: corrected the date.
I am less than a week into my Visual Basic education. I have downloaded Visual Studio 2008 and am teaching myself Visual Basic 2008 in hopes of landing a particular contract position.
In the meantime, a friend of mine told me that it is not recommended to write a Windows Service with Visual Basic. Is that true? Could he be referring to some much older version than 2008? Does the .NET version come into play?
What is at stake is that the company that my friend works for is going to completely re-write a component of their flagship product at great cost and expense and simply abandon their existing VB code. If the only hang-up is getting it to run as a service then they could save a lot of money if Visual Basic could, in fact, run reliably as a service.
You can write .NET services in any CLR language, including VB.NET --- your friend was thinking of VB6 and earlier.
(I do recall some fairly crazy kludges that allowed services to be written in VB6, but for all practical purposes, services written in VB6 weren't really a viable solution...)
There is no reason that Visual Basic .Net can't write a windows service. You can select a project which will create a windows service under the "Windows" projects in the Visual Basic section.
Writing a Windows Service in VB.NET (using any version of Visual Studio >= 2003) is just as effective as writing a Windows service in any other language.
Your friend may have been thinking of Visual Basic 6...or he's partial to another .NET language.
In either case...you should be fine to keep going on your path the way you are.
Your friend may be referring to Visual Basic, not VB.NET.
While VB.NET has syntax that is similar to Visual Basic and some convenience functions are still present, they are two entirely different languages and environments.
Your friend is correct in stating that Visual Basic (meaning 6 and earlier, not VB.NET) is a poor choice of a language for a service (or any new application), but VB.NET is every bit as legitimate as C# or any other CLR language.
It may be useful to refer to what you're learning as "VB.NET" or "Visual Basic .NET", rather than just "Visual Basic".
.NET certainly allows you to use Visual Basic to write a Windows Service. I believe there is even a default project template to do so. Here is an tutorial as such: http://www.vbdotnetheaven.com/UploadFile/mahesh/Winservvb11172005233242PM/Winservvb.aspx
All .NET code is converted to an intermediary language that is executed, thus all .NET languages can be used to write a windows service.