I'm converting all of my Windows XP production applications to Windows 7 and I am having a couple of problems.
1: Whenever I get an error, on the XP machines, it breaks execution and stops on the line of code with the problem. In Windows 7, it just throws a generic exception and I have no idea where the line of code with the error took place. Very frustrating.
2: In XP, I can edit changes on the fly while I am running code if I place breakpoints or follow along the code. If I try that in Windows 7, it says that's not allowed with 64 bit applications.
I want to learn 3D programming within the Microsoft Windows .NET environment. My best .NET language is VB.NET.My aim is to be able to create 3D images only. I do not want to create 3D videos or 3D games.Any suggestion of books or online resources that are suitable for VB.NET users like me?
UPDATE:
I know nothing about 3D programming and only have limited experiences in 2D graphics programming under .NET I can work in all versions of VB.NET and Visual Studio (2003-2010)
Background: I have 2 Apps. One spawns the other as a 2nd process. Both need Adminstrator rights to run.The below code (which spawns the 2nd app from the 1st) works just fine from my released Application (when I right click the 1st app icon and start as Administrator).
Problem is, from within the VB Express environment it does not. The 2nd app starts, then complains about Access Rights.Can I start a process with Administrator rights in Windows 7 from within the environment?
Overreaching amateur developer that is outsourcing some of my work and doing part of it as well. I've been working on a dictionary/ thesaurus / spell check & suggestion application that I am trying to get to work on all applications within the windows environment.
I've used hooking to get key stokes and show output as the person is typing for definitions and spelling suggestions. This isn't accomplishing everything I want. Works fine for spell checking and suggestions but to click on a word that already exists or for touch screen interfaces to touch a word it doesn't work.
I was reading the Raw Input API on MSDN and thought that would work but my developer that I've hired is advising me that the RAW input's scope is only on the window that has focus and so cannot do low level hooking. I'm considering giving the effort but wanted a 2nd third fourth perspective prior to making the effort.[URL]
I have VB6 Dll which I am referencing in vb.net ,I am calling the following function in it. It working fine in developemnt environment but not in deployement environment.
Error Method not found: 'Boolean MyUtils._MyUtils.LoadMyObjectRecords(ADODB.Stream ByRef, System.Array ByRef)'.
I am trying debug my program on a Windows 7 machine. My program reads a txt file using TextFieldParser
I get an error message when I try to open a file
Could not find file C:UsersBillDesktopprogram name TextFieldParserinDebugFileName.txt.ReadColumns
Code
Dim safeFileName As String = IO.Path.GetFileName(Me.OpenFileDialog1.FileName) Using myReader As New Microsoft.VisualBasic.FileIO.TextFieldParser(safeFileName)
It doesnt get past the second line, which tells me there is something wrong with the way i am getting the file??
I am not getting the location of the file just the file name
I upgraded to VB2010 from VB2008 early this year and have been working on a Windows Service which I am now debugging. When I was using VB2008 in Windows XP SP3 I would put a Stop statement in the code and when execution got to it a dialog would open asking if I wanted to debug it using a development environment listed in a provided list. The list contained the VB2008 VS IDE which I selected which would in turn transfer me to the IDE in debug mode. I was very happy with this setup.
Now I am using VB2010 with Windows 7 and when the execution reaches the Stop statement the service just stops. It no longer offers the choice and ability to "jump" into the development environment via the dialog that I mentioned.[code]...
I'm developing a Windows Service in VB.NET 2008, but I feel like I'm going to have an aneurysm. To debug the service, I've added a 15 second wait to the initialization code, which gives me time to start the service and attach the .NET debugger before anything happens, so I can hit breakpoints and such. I really miss "integrated" debugging with this type of workaround, and testing seems to be a huge pain.
What's the best way to do "regular" debugging of a Windows Service that's in development? One option I'd considered was moving all of my logic to a DLL project, leaving only control logic in the service itself, and then creating a Forms project that essentially just had "start" and "stop" buttons on it, and called into the DLL to do everything else. This way, I can debug my code normally, and then just deploy the compiled service when the DLLs are ready.
I'm developing a Windows Service in VB.NET 2008, but I feel like I'm going to have ananeurysm. To debug the service, I've added a 15 second wait to the initialization code,which gives me time to start the service and attach the .NET debugger before anything happens, so I can hit breakpoints and such. I really miss "integrated" debugging with this type of workaround, and testing seems to be a huge pain.What's the best way to do "regular" debugging of a Windows Service that's in development? One option I'd considered was moving all of my logic to a DLL project, leaving only control logic in the service itself, and then creating a Forms project that essentially just had "start" and "stop" buttons on it, and called into the DLL to do everything else. This way, I can debug my code normally, and then just deploy the compiled service when the DLLs are ready
I have the Immediate window option available in my menu, but when I click it or do the keyboard shortcut, nothing happens. It's quite difficult to debug an application without an Immediate window.I've tried resetting my settings to general developer and all of the other suggestions I found on the web, but still, no immediate window shows up when I click it or do the keyboard shortcuts..
I've just installed Visual Studio 2010 Express on a new laptop running Windows 7 64 bit.
When I debug a VB project and an error is encountered a message is sent to the immediate window, but execution is not halted. This means I am unable to look at variables etc.
I have a procedure that loops through the directories/subdirectories on a file server and sets the permissions. Procedure is called on a button click of a form.
I need to display on the form which directory is being processed. Similar to if we use the Debug.writeline which writes to the output in Visual Studio. I tried using a ListBox but it only displays the last one and only displays the last one once processing is done. I want to be able to display each directory name as it is being processed.
Psuedo code as follows:
For each dir in L drive
setPermissions(dir) 'display in ListBox dir name lstProgress.Items.Add(dir.Name) Next
FormA calls DialogB where user cancels DialogB which exits via ForceTermination(), see insert.Caller FormA check for DialogResult not = OK, which it isn't, and I can see this in debug as Abort(3).However, the code continues merrily along its way until I get a 'null reference' error which I'm trying to avoid via Force Termination().This is caused by the user cancelling DialogB, a selection process to get a database (SQL) instance.[code]
I've googled a bit and saw someone said they had success in simply dragging the .dll files over to their application's path. I have tried this as well, and unfortunately it doesn't work. It stops the errors, but my chart is entirely blank. Some of the features of the chart work. ie: the legend shows up. But I have hidden some items from the legend and they still appear in the legend while running on a 2.0 system. For example, on my development machine, it shows 4 items in the legend, but on the 2.0 machine, there are all 7 - including the 3 that I have hidden.
i need to change the "PATH" environment variable in a VB program (Visual Studio 2008). Here is the code i use to add the "C:TEST" folder at the end of the existing one.
test Dim PathVal As String PathVal = Environment.GetEnvironmentVariable("Path", EnvironmentVariableTarget.User)
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?
I'm looking at implementing a piece of software I've created into a new environment. It is currently accessed via network share by users who have full administrative permissions on their user accounts. These same users will have their accounts locked down excessively. I am wanting to consider now before any changes have been made, any code changes I will need to make as my application makes use of a lot of features that admin users take for granted such as registry editing. My program is running through the .net 3.5 framework and is being accessed on XP machines.
Had this matter on Xp machine and visual studio 2010 ultimate after windows update between december and january: even the simplest windows form program crash on start when starting for debug (inside Ide, F5) unless putting breakpoints on each line of the autogenerated (and marked as "debugger step thorugh") code.(see: [URL]) I was wondering if this matter affects only Xp machines, or if someone with Seven or Vista had same matter.
I have written a fairly basic application. It reads txt files, loads a SQL, and outputs to text files. The application compiles and publishes without an error. The app works perfectly on my PC. I can not get it to work on any other PC. Application will install without an error but when I try to launch the app, nothing happens. Running out of ideas to try and hoping someone may have some tips or tricks to try and see what is going on that I have not tried.I am running Windows 7 Pro - 64 with Visual Studio 2008. The only references are for .net 2.0 and ADODB.DLL. I have setup the app to include all references as local copy to true.
I have tried installs on Windows 7 Pro, Windows Server 2000, Windows Server 2003, Windows XP Pro, and Windows Vista. All install without error. Have tried installed as user with admin rights and the PC's primary admin account. When you launch the app, there are no messages in all OS except Windows 7. It will basically Flash a message about checking for compatability and run you through a wizard to see if running as XP or Vista works and it doesn't.
I've started a project in Expression Blend and has been working the codes in Visual Studio 2008. It was alright, no problem. I've worked heaps of projects like that before without any problems. However, out of nowhere, my WPF designer in VS2008 now gives me the following error:
Object reference not set to an instance of an object. at MS.Internal.Package.VSIsolationProviderService.CreateIsolationProvider(String identity, AssemblyReferenceProvider assemblyReferences, IEnumerable'1 assemblyFolders) at MS.Internal.Providers.VSDesignerContext.GetIsolationProvider(IServiceProvider provider, [Code] .....
It displays the above instead of displaying the WPF designer. Also, I cannot Debug>Start Debugging the application anymore. I can still run/test/build it in Expression studio though. The funny thing is that if I restart a project in Expression blend, copy all the xaml codes, and copy all the vb .net codes from the original application, it works for some time, and then afterwards start giving me the same error at wpf designer in VS2008.
I have a VERY perplexing problem in both Visual Basic 2008 & 2010 Express. When I try to debug my project, the program runs without stopping at any breakpoints. If I start the debugging by clicking on Step In, the application just starts running.The Immediate Window has the following line, when I start debuging with Step In:Step into: Stepping over non-user code 'QBPOExport.GlobalFunctions.Main' (QBPOExport.GlobalFunctions.Main is my startup task)
I am going nuts here. First time trying to debug an app that uses threads. I have a console application with a thread that calls Sub (Sub A) from a thread. I have been able to get the debugger to stop on breakpoints in Sub A by setting the condition to "Test" = Thread.CurrentThread.Name (and naming the thread "Test") Using a normal breakpoint does nothing.
However, in Sub A after it hits the breakpoint, any stepping (F10, F11) causes the Sub and app to exit instead of going to the next line of code.There is an IF / ELSE statement in Sub A. I have put a System.Diagnostics.Debug.WriteLine statement in both the IF / ELSE blocks, yet none of this code executes. Sub A calls a webservice, so I initially thought something might have been crashing in that, so I tried running Sub A without using a separate thread and everything works as expected. Do I need to change some setting in VS2008's debugger?
Ok hard to explain this one, it may be the codeproject addin i added recently or its a setting i have changed somewhere but when i'm debugging my app opens up many .cs files, kind of interesting but when i want to step through my code it goes into these files and when it errors it has no reference to where the error actually is. sometimes these files being opened have errors on them which i have had to correct for the code to work.
Has anyone seen this before and what could i do to stop it, i wish to confirm that it is this addon before i remove it (which i will do if it is this addon causing this).
I have a UserControl that retrieves a bunch of data from a database. It uses the current date as one parameter to determine which data to show.
The database however is a little old and has no data available after April 2009, so while debugging I cannot get any data and hence I can't test the control.
As a solution I simply used a date in the past instead of the current date, just so I could see some data. Obviously, this has to be changed in the release version of the application, but I'm worried it will be forgotten, leaving the control completely broken, and worst of all, it's very hard to tell that it is returning the wrong data, so the users won't see the problem at all.
Now, I'm looking for a way to change the date used during run-time. A property in the UserControl would be the best solution for me. I could have a property UseTestDate or something, and if that was True, the test date was used. It would be set to False by default, so that the regular date is used by default.
The application has a Property Grid which is used to change the properties of the UserControl, so that's how the (test!) user can change this property. He can choose to show the current date (but there probably won't be any data preset), or he can set the UseTestDate property to True and get some old data.
The problem, obviously, is that the end user in the final application will also see this property in the grid! I don't want that obviously, there is no need for them to use a test date.
So I am looking for a way to make this property visible only when the application is run in DEBUG mode (via the VS IDE). I can make a property invisible simply by setting the Browsable attribute to False. I simply don't know when to set this. The attributes only allow a constant, so I cannot use a variable that is True when the application is in debug mode or something.
I tried simply putting the whole property between a conditional compile statement:
#If DEBUG Then Private _UseTestDate As Boolean Public Property UseTestDate() As Boolean
[code]...
I am able to Run the application in debug mode, even though there is the error that UseTestDate cannot be found. It seems that the property can be found when I run it (which makes sense of course, as it's only compiled when in debug mode). However, using that code I am unable to Build the application so I can run the executable; the error does not 'vanish' then...
So, how can I build an application that uses a property that is only compiled when the application is run in debug mode?
I'm using VB2008 SP1 Express. My app downloads a file from a FTP and compare inside it the registered values,but some users have problems when validating the key,finnaly I found that the following code evaluates TRUE
