I have generated a component in Delphi 2007 Code Gear and I need to migrate it to .NET to be used by VB.NET platform.I generated an ActiveX dll but I have been told that only the declaration of the class is visible in .NET.Actually the component I have generated is inherited by another component of which I have only the .dcu files. My new component is exactly similar as the parent one except from that I have overridden the constructor create.I wonder why the .NET, although it accepted the component, it did not provide the inherited properties, methods etc.
I am converting an old Vb6 solution to .net 2.0 in vs2010. I've been working in C# for about 3 years now and .net for 5. I don't recall having this problem in C#, but if I want initialize a readonly collection of DerivedControlFoo Is there a clean way to do it besides creating a sub to do it all off somewhere else? I'd love to be able to do it at the class level at the declaration for readability and simplicity.
Create a DLL component for database operation and use created component in another project. Required methods, events and properties
a. Connect b. Add c. Delete d. Save e. Record navigation (first, next, previous, last) f. Properties for all database fields g. Events for validation of database fields.
I am using Delphi 7 to try to use a .DLL created by VB.net. When I run TDUMP.EXE on the .DLL, it reports no exported data available. The VB.Net .DLL uses "RaiseEvent" to return data.[code]
I've created a component whose name I'd like to be able to change while editing in the component tray. I've added a Designer action for a name property, but now I'm stuck.
Looking at the property grid, I can see that the name property is parenthesised, indicating that it's not a regular property.
.NET converter (either C# or VB.NET)? I've inherited a bunch of Delphi code, never seen Pascal before and rather than learn it, I'd rather just try to use an automated converter, if available, and clean up the code after that. Can't seem to find this kind of tool anyway I search
I have built an Access 2007 database with some data stored in it. I have managed to export data using VB2008 from that database to Excel 2007 and have it automatically draw charts based on this data and a query in the Visual Basic Code. One of the results looks like this:
I am going to be taking up a new job as a VB.net developer. I have worked with C# for about 3years. I did mention to the interviewer that I haven't worked with VB.net, but he seemed to think that its easy to migrate from C# to Vb.net.
how I can prepare myself for this job? Any good books or websites on this area? How different is vb.net from C#?
I have been using COM+ components(using VB 6.0) in my existing web application developed using Asp/sql. I'm basically using COM+ to get the benefit of it's inbuilt Transaction Management feature which is useful when you are performing some set of actions across different databases simultaneously.Now I want to migrate my existing site to the .Net Framework.
I've designed a Windows Service in Visual Basic 2005 that needs to call some functions from a DLL written in Delphi 5. If I try to add this DLL as a reference, I get this error:
"A reference to 'C:ProjectsServiceProMDPUpdateServiceMessageStubApplicationSPHost.dll' could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component."
I assume that it is just not possible to add this DLL as a reference to my VB2005 project, since the DLL was written in an old version of Delphi, correct? This isn't a big deal, as I can just use the DllImport function from System.Runtime.InteropServices, but if it is possible, adding it as a reference would be preferred.
My other question is, how would you be able to call a function from the DLL using DllImport, if the function you are trying to call takes a Delphi record data type as a parameter (if this is possible)? If possible, would I need to pass each field in the record separately or would I be able to define a structure in my VB app that mirrors the record definition in the Delphi DLL and pass that? Or, would it be best if I just created another function in the Delphi DLL that took various string/integer/boolean/etc. parameters that I could call from VB that would then call the original function in Delphi? I tried searching the internet for this specific question, but I couldn't find anything that looked useful.
I've gotten a DLL from a supplier. Most functions I can call just fine, but some crash (System.ExecutionEngineException, doesn't even do with a try-catch...). The thing is that the ones that work are called with simply types, and the ones that crash have a type/class/structure in it.The documentation states how to call with "Visual Basic" without stating version. Here's how it looks..[code]I did figure out to use "Integer" in stead of "Long" and the strings needed some work but are fine now.Now... The "Type" doesn't exist in VB.NET so what should I do. Tried a class but that didn't work.I can call the DLL with "bad" data and get a good reply, eg "this and that is wrong with the input", but when I set that straight it crashes. I suspect that it's when it starts to write in the memory allocated by me and that does not match what the DLL expect.
BTW when I look at the class I made, I can see that - at least VS - lists the members in an alfabetical order. Is that how it's arranged in memory and could that be the problem if the order is different from the one expected by the DLL. I would epect that the total size was the same irrespective of order, so the problem would arise when I try to read the data and I would get junk.
I get to convert a Delphi application to VB.Net.My last project i had to convert a Java app to VB.Net.Anyway I have most of the application converted however there are a few items that i have been unable to find the .Net equivalent. Most are from the Delphi. Sysutils class.
Dim ThisModule As IntPtr Dim Proc As Process() = Process.GetProcessesByName("Sol") For i = 0 To Proc(0).Modules.Count - 1
[code]....
I have made this code, and works perfectly, but now... i want to make it in Delphi, the problem is... i have not the enough knowledge for make it, and... in google, i haven't found the information i need.
I've got some functions I need to call that are in some DLL files that have been written in Delphi 5 in a VB.NET 2005 application. I'm able to use the DllImport function to access the functions just fine; however, I'm having an issue with the Delphi string data type and passing it to and from the .NET application.
[Code]...
It takes two string parameters and one double. I can call this function from VB.NET just fine, but it will error as soon as it tries to use one of the string variables (so in this case, when it passes them to another function) and I've found that the string values in Delphi are junk when they've been passed to .NET. I'm guessing that the string objects behave and/or are encoded differently between .NET & Delphi 5, and that I have to apply some sort of Marshaling to the function parameters in .NET, but I've tried all of the different types of marshaling and nothing has worked. Unfortunately, I haven't been able to find anything about this issue on the internet.
Does anyone know how I can call this Delphi function from .NET and have it pass the string values in a manner so that they won't be corrupted when stored in Delphi?
I have a Delphi written DLL that exposes some interfaces to a vb.net application. The interfaces inherit from IUnknown (but this could be changed if required), simplified example:
Now I want to transfer a collection of IWindow to vb.net, and in the vb.net application I want to be able to loop through it with a for in loop.
I read that it's possible using IEnumerable/IEnumerator but I don't quite understand how to implement them. Are there any good tutorials about this, specifically showing the declarations on both side? Example code would be great.
Please note that I prefer not create a com dll that should be registered and imported. Currently I export a function that enabled me to obtain an interface.
I have a Delphi program that communicates with a vb.net dll that I created. The vb.net dll communicates with a Fluke scope meter via an RS232 connection. I have created a program that communicates correctly via RS232, giving me the anticipated value. Though, when I package this up as a dll and access the dll from my Delphi program I always receive a value of "1", rather than the value I was expecting (most cases a value in and around 240).I know that my delphi program is definitely communicating correctly with the dll and that my dll is definitely communicating with the scope meter
Here is my vb.net code: Public Interface IFlukeComm Function GetReading(ByVal Command As String, ByVal PortNum As Integer) As String
I have an old program from 2002, which was coded in Delphi 7. Now i would like to rewrite the whole program, and expand in Visual Basic. how to convert my old code to VB2010? The code is very simple. I fill a database with Comboboxes and TextBoxes .Text. [Code]
In Delphi when we needed to allow the system to finish painting an object or something like that we could add a processmessages that would then let the system finish what it was doing before going on with the code.This was always handy when we wanted to show a message like "Please wait"before the start of a lengthy process.So then. What is the equivalent way of doing this in VB.
I have the following code that I need to migrate from VS 2003 (.Net 1.1) to VS 2008 (.Net 2+)but I get compilation error System.Xml.Xsl.Xsl Transform' is obsolete: This class has been deprecated.I probably need to use System.Xml.Xsl.XslCompiledTransform instead.but I do not find the matching Load() and Transform() overload versions that I can use with all the parameters of my original code.in MSDN [How to: Migrate Your XslTransform Code] I only found some simpler cases.url...but in my code I see some remarks that hints that the added parameters were used to avoid exceptions, so I prefer to use these parameters.[code]
I have a legacy VB6 ActiveX control used in IE to provide control of a parallel-port device from a browser application. I wrote this thing about five years ago; It's a pretty simple control, and it doesn't require a lot of maintenance. However, I've noticed that running the VB6 tools is becoming more and more painful over time, so I'm looking at the possibility of migrating this code to VB.net 2008.This thing is super-simple. It implements IObjectSafety and exposes a single public method, which we call using Javascript. The control has no UI other than a single box with a caption that displays its name and version number-- useful for troubleshooting deployment issues.
How would I create the equivalent in .net? Am I creating an applet? Or a .net Assembly? Any gotchas to look for as I try to make this transition?(I should make it clear here that I'm not either a VB6 programmer or a .net developer-- I've dabbled in this stuff but it isn't my area of expertise, so go easy on me).
I have an ASP.NET in VB code base that if I open in Visual Studio as an existing website works and tests just fine. I have followed many tutorials for porting this over to Azure: -Tried create new Azure project add a webrole and drag and drop project files into the new webrole, but I get about 300 reference/missing stuff/etc errors -I have also tried creating an azure project under the website solution but the option to add the website to the webrole by clicking "web role project in solution" is disabled/grayed out I have been able to make the configuration files and compile through the command line but this does not work with visual studio so I am unable to test before deploying into staging
I have some questions: 1) What's the learning curve for someone with good background in VB6? 2) what are the main advantages of VB.Net compared to VB6 and what will I be missing from VB6? 3) With VB.NET 2010 "ultimate" edition is it possible to make stand alone apps or they will be depending on net anyway even for the EXEs?
