This is a dumb question, but I just cant find an answer. I want to do something as simple as this in IronPython, something I did in asp.net vb.net to capture the id of a table displayed in a gridview or datagrid
I have been writing a COM callable assembly for my current solution allowing unmanaged code some access. I have just been told that I can now start using 3.5 of the framework having used 2.0 for some time.I then came across WCF and was wondering if I could use any of this to create my application api and allow access from anmanaged code.
I have created a COM callable assembly which consists of an Interface, a single class which implements the interface. In this case the implementation is a single method.I have registered the assembly, created a type library and added the assembly to the GAC.I thought about opening an Office application like WORD or EXCEL 2003 and trying it from there but beyong referencing the COM assembly I have no idea how to code it.
I need to create a DLL that's callable from C, that executes database queries and returns results. The first tool I reached for was VB, and I found it easy to create a DLL, but when I view the DLL using dumpbin /exports, I don't see any functions.
So, my questions:
1) Is VB the right tool for the job? If not, (The ideal solution would be a 3rd-party DLL that will let me do database queries -- a friendly higher-level wrapper above ODBC. I've searched around and come up empty, but maybe I haven't looked in the right place).
2) If VB is the right tool for the job, how do I export a class method so that it's callable as a function in a legacy C environment?
More details:
1) The target environment is Mercury Loadrunner VUGen. It's able to import DLLs and make function calls, but the environment is (non-.NET) legacy C.
2) My development environment is MS Visual Studio 2008
My windows application needs to raise an event in a COM callable assembly so unmanaged code can pick up on the event.I am sick of this. All the crazy tags required for COM callable is doing my head in.
Simple question that does not seem to be covered: If I use a lot of Debug.WriteLine statements in my code, will they be completely absent in my production version?
I mean: Is the compiler smart enough to not emit any code for those calls? Or would I have to surround them by #if DEBUG..#end if directives?
It run smoothly for the first time,but when I execute it for the second time,it occured the following errors:Unable to copy file "obj\Debug\FYP.exe" to "bin\Debug\FYP.exe". The process cannot access the file 'bin\Debug\FYP.exe' because it is being used by another process.
Is it possible to assign a value to a class variable from inside a #IF DEBUG conditional? Basically what I want to do is conditionally execute some code from inside my main form load if I am running in DEBUG mode.[code]However, it seems like you cannot assign a value to a variable. I'm obviously not understanding the scoping correctly.I cant seem to put the #if DEBUG inside the Load.
I have a simple application:Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
#If DEBUG Then lblDebug.Text = "Debug" #Else lblDebug.Text = "Not in debug" #End If
Now when I run it in VS, it prints "debug" like it should, but if i run the .exe, it still prints "debug". What do i have to do to get this to work right?
How do I select DEBUG or RELEASE configuration in Visual Basic 2008?The drop down list Project > Properties > Compile > Configuration that was in Visual Basic 2005 is gone from Visual Basic 2008.software developer
Im using Visual Studio 2008 in Windows 7. Recently I cannot debug(F5) any projects because this following error is appearing
Error while trying to run project: Could not load file or assembly 'WindowsApplication5' or one of its dependencies. The module was expected to contain an assembly manifest.
I have a program written in VB.Net (Visual Studio 2008) that uses a DLL written in Visual C++ by another developer. I'd like to be able to step in to the C++ code as my code makes calls to methods in the DLL. Since the DLL is it's own solution, I don't think it can be included in my solution/project. I tried putting the DLLs pdb file in the debug/bin directory with the rest of my build and pdb files. However, when I get to the point in stepping through my code, and it gets to the dll call, it just steps right over the dll code. Do I have to manually load symbols?
I have built/rebuilt the files sevaral times.I have also renamed the file in the debug *.exe.The NetworkAssociation.exe file is in the debug folder.[code]
I am trying to use #If DEBUG Then to show a designer view of a report in Debug mode, and to show a print preview otherwise. The 'Define DEBUG Constant' is ticked in the Project Settings/Compile/Advanced Compile Options.But when I run the exe I cannot see the difference that I want. Has anyone used this, and do you know if I am missing some setting, or whether I have to turn off the 'Define DEBUG Constant' setting to get this to work?
I want to know how to use DEBUG const in DLL.-> I have a web application in vb.net-> I have a DLL whith some function.Now i have reference this DLL into my web application. And now i want to check in dll whether my application is in DEBUG mode or in Realease mode.Second thing i want to check some validation in constructor based on that constructor will throw exception and i want to show it on page without handling. I have used try catch in constructor and not used in page, so it will give me error in dialog box not in page.
I have an ASP.NET C# project consuming webservices and WebMethods are wrote in VB.NET with source code on a local IIS server. The WebMethod returns null, and I want to debug it to know why I get this.
I was running Visual Studio 2008 on my computer went through a whole VB progamming course with no problems. I recently had to have my computer hard drive erased and reloaded with windows xp to eliminate a virus. When I got it from the shop Visual Studio 2008 had not been backed up so I reinstalled the Professional edition from my disc. I opted fo the recommended installation. Every thing seems Ok except when I put a debug.Writelie (" Hello"} in the code nothing appears in the immediate window when it is executed. If I go to the immediate window and type the same line and hit return the string appears in the immediate window. If I assign a value to a variable in the program and put the debug.writeline command in the code module nothing appears in the immediate window, but if I go to the immediate window and type debug. writeline (var) and hit return the value of var apppears in the immediate window. i went to the debug menu and selected windows then clicked on immediate but it didn't highlight or show check mark. When the project builds after start debugging the immediate window appears. In the help it talks about a trace listener and insertig a line of code in the compile command line.
so my data layer works with functions that return datasets. These datasets are generated by passing a stored procedure name, and a parameter array. Works absolutely great. Now, in my stored procedures i do a couple of print 'something' statements as part of a debug process. Is there any way I can read this information from .Net? Obviously, the select statement is returned to the dataset. what would be great is if I can create a log file, that prints the other info that i return via print.
below the str which rs.Open(str, conn, ADODB.CursorTypeEnum.adOpenDynamic, ADODB.LockTypeEnum.adLockOptimistic) there is a debug on it,.please what should i do? [code]
I'm trying to debug an application as I did before using vb6. Placed a break point in the code and run. when it hits the breakpoint I tried to modify the code but, it does not allow it.
I got a message saying Changes are not allowed in the following cases:When the debugger has been attached to an already running process The code being debugged was optimized at build or run time
The assembly being debugged is loaded as domain-neutral
The assembly being debugged was loaded through reflection
I have a Dll project written in VB.Net 2003 which compiles a Dll used in other projects. I need to debug this Dll while it is being ran in the other project. Does anyone know how I can do this, or do I need to integrate it into my other VB project somehow before I can debug it?
In the past, perhaps versions of Visual Studio prior to the 2008 that I am using now, I would do something like this in my VB.NET code:System.Diagnostics.Debug.WriteLine("Message")
and the output would go to the output window.Now it doesn't. Something must first apparently be enabled.
If this involves "attaching a debugger", please explain how to do it. It seems to me that it should just work without too much of a fuss.Here's a video explaining the issue in real time and showing you all my settings[URL]..
how can i add a method to the debug namespace in vb2008?i've seen some examples of extension methods but they all extend strings.what i want is to add a .clear method, to the debug namespace.i've got the code that clears the immediate window, but i'm unsure how to add an extension.