This problem is pretty self explanatory. Here are the details: I'm trying to include freeglut and glew in Visual Studio 2012 on Windows 8. I'm on a 64 bit system, so I thought I needed to put glew32.dll in my 64 bit system folder. I tried that and receive the following error:
"The application was unable to start correctly (0xc000007b). Click OK to close the application."
Which I've interpreted as I'm trying to put a 32 bit dll in the 64 bit folder or vice-versa.
Just for laughs, I tried putting the file in System32, but of course, it just told me the file wasn't on my computer. Any suggestions?
EDIT* May I also add that some of the set up for this was NOT the same as it would have been on Windows 7 or Visual Studio 2010 or earlier. I may have missed something because I kind of winged it using the search function combined with some documentation I found on various websites. (i.e the lib and include folders are no longer in the same place)
EDIT2* I'm sure this can probably be derived, but I want to add it anyway for clarity: If I removed the dependency for glew32.lib and comment out any code using glew.h, the window forms as it should. I don't think my source code is needed seeing as I'm 99% sure this is not a code issue, but if anyone wants to see it, let me know and I'll attach it.
Related
I am using VBA hosted in a drafting program called MicroStation. I have been using MSCOMCTL for the last few years to use controls such as Tab Views and ListViews. I have come back from a work trip and found my home PC to have a Windows Updated and im assuming that its broken it as i have found many articles relating to similar problems.
MSCOMCTL will register and says it has succeed, but still shows as missing in the VBA IDE. Usually i can just use the regsvr32 command and it will work no problems.
I have researched alot and have found a heap of solutions, but none work for me. The main one seems to be to run.
regsvr32 c:\windows\syswow64\regtlib.ocx
But i cant find regtlib.ocx on my Windows 10 - 64 Bit PC.
With this VBA Program, the company where it is deployed is very restricted on what the users can do so im hoping to find an alternative to MSCOMCTL but still within VBA that i can somehow package / compile within my VBA file and doesnt need to be installed onto the PC. Either that or a solution to get the file working. I have been reading article after article and trying a heap of things over the past few days but nothing has worked. It seems at the moment that my best option is to redesign the forms without the Tab Control and List Views. But i find this crazy as they are microsoft files.
Thanks in advance!
So far i have tried the below (plus a couple more escape me at this time)
*Replacing MSCOMCTL.ocx with a downloaded version (backed up the original just in case)
*Replacing MSCOMCTL.ocx with a version installed with Office 2013, located under the program files x86/office/root etc.
*Registering MSCOMCTL in safemode to ensure it wasn't in use.
*Searching the C drive for regtlib.ocx as that has been known to fix it.
*I did find an alternative, but requires various files to be installed onto the PC which wouldn't work in this case with the company's restrictions
*I know this is not a new issue, but most of the posts are a few years old and their solutions (usually re-registering the file) have not worked for me.
Thanks everyone. Problem has been solved. It was a combination of a couple of things based on dbmitch's answer.
By unchecking the missing control, closing down the host program and rebooting. Then opening up the VBA file and searching for the "Microsoft Common Controls" and selecting it. Even though the text was the exact same as the "Missing" one it seems to have done the trick.
I did do that step, but didn't close down the program and start again in between.
Thanks for your help guys!
Recently I noticed in my current vb.net project that sometimes (depending on the value), if I enter a double value the editor changes my input, for example:
When I type ...
Dim x As Double = 0.6
...after commiting the line by pressing Enter it becomes:
Dim x As Double = 0.59999999999999998
If I directly undo the action, then it gets reverted back to the original value I typed in. Any future edit in that line will again produce the undesired results.
I'm aware that internally 0.6 is calculated as 0.59999999999999998 so it doesn't make a difference for the running application, but it's very annoying and the strange thing is: this hasn't always happened and, if I create a new project, it doesn't happen there either.
So my questions are: How can I prevent VS from doing this? Why does it happen at all? Why isn't it always like this (previously in my current project or in a new one)?
I'm running 64bit-Windows 8.1 on an Intel CPU - if that has anything to do with it.
Has anyone got any ideas?
EDIT: I'm using Visual Studio 2013 Professional (12.0.31101.00 Update 4) and, yes, the project has been migrated from several earlier VS versions. There are no relevant Add-Ins or extensions installed. Disabling "Pretty Listing" does indeed prevent the problem, but of course then the other highly useful aspects of the option are disabled as well :o(
EDIT2: After the tip leading to "Pretty Listing" I found the following SO article, but there also no solution was found: Visual Studio VB pretty listing settings
Several years ago I had a project where this was happening. As you wrote, the reason for the number is that some numbers can't be represented exactly in a binary floating point variable. More on this here.
My project had been upgraded through several versions of Visual Studio. It was also shared with developers using VS Express.
If I ran into this problem again today I would open and check the project-file manually, or just simply create a new project and re-add the files if I could not quickly locate the problem and the project was small enough.
If you have upgraded the project through multiple versions of Visual Studio like I had, it might be dragging some settings along that are no longer visible in the projects options dialog.
Just as an interesting experiment you could also try to turn off Visual Studio's Pretty Listings to see if that is what is actually changing your code.
I am working with visual studio 2012, and my problem occurs in a large, old winforms application solution when I try to compile the whole application (dozens of projects).
When I get the latest code from source control (Team Foundation Server) for the first time, and build the solution, it builds just fine the first time. Then, if I make any changes, a later Build/Rebuild, will sometimes (not always) result in lots of projects in the solution throwing the following error for some of its resx files.
Unable to create a manifest resource name for "Contracts\Templates\ContractTemplateDb.resx". Could not find a part of the path 'C:\Windows\system32\Contracts\Templates\ContractTemplateDb.vb'
OR
Invalid Resx file. Could not find a part of the path 'C:\Windows\system32\NeptuneForms\HelpForm.resx'.
The problem is that there is no reason it should be looking in C:\Windows\system32 for these files, as they exist fine (and did during the last build) in the local directory of the project! The random directory is not always C:\Windows\system32, sometimes it is a random directory of another project, or even in another branch.
This happens sporadically to some of our developers, frequently to others, and almost always to me, and it seems unrelated to the code we are writing, because when it happened, I rolled back all the changes we had made since it started happening, and it still happened.
There are two things I've tried, that had no success.
Recreate the entire solution, and remove and readd all resource files as though they never existed before.
Install all windows updates and get the latest updates to Visual Studio 2012
Nothing has helped, and I am at a loss. My next step is to upgrade to 2013 and hope for the best, but I'm afraid thats not going to help either.
Does anyone have any similar experience, or any ideas of other things to try? I'm pulling my hair out over this one...
I'm kind of new to Visual Studio. I've built a few simple programs in it, but now I'm in the process of rewriting a huge system I wrote in VBA. What is frustrating me is the Error List in VS is only listing errors for one .vb File in my project, lets call that VBFile1. Now, when I work on another vb File, VBFile2, which is in the same project as VBFile1 no red squiggles or errors are listed for VBFile2. I don't understand how this could happen. This is what I've tried/checked:
Filter is set to 'Current Project' and I played around with the other Filter settings but no change.
Checked the Text Editor under Options and according to the research that I've already done it is fine. Plus, I have never changed any of these settings anyway.
Closed and re-opened Visual Studio.
Closed all open files in the Project and still displays the same error list
Close all files except the VBFile2 but still shows the same error list of VBFile1.
I have Visual Studio 2012 Ultimate. I feel like this should be an easy fix...I just am really confused what's going on.
Hope this makes sense!
UPDATE: Excluded from project, VBFile1 and finally errors are listed for VBFile2...why would this be?
I am not sure if it has been fixed in Visual Studio 2012, but there is a Connect Request for Visual Studio 2010 with a resolution of won't fix because of performance issues. The effect your are seeing is because you have exceeded the maximum number of errors for that project (what I am used to seeing is 102 as the threshold), it will not show you anymore till you fix the ones that it has already shown you.
According to this MSDN article, which I found through this SO question the limitation is still there for the IDE but has been removed for the command line compiler.
From above MSDN Link:
Limitless (Command-line) Errors!
This is actually a good thing, let me explain. For performance reasons, the Visual Basic IDE maxes out at 101 errors (with error #102 being “Maximum number of errors exceeded.”) This can make it difficult to estimate the amount of work remaining in certain situations, particularly in upgrade scenarios. We have removed this limit from the command-line compiler in this release, though it still there in the IDE. What this means is if you want to know exactly how many errors there are for a project, just invoke the compiler through msbuild.exe or vbc.exe and you’ll get your answer.
I downloaded the Kinect for Windows SDK as well as Visual Studio Express 2012. I installed some of the WPF applications from the SDK browser and they worked wonderfully with the sensor.
Problem is, I open up the .sln to explore how these applications are built and I start getting broken references immediately without having changed anything. I can hardly open any of the XAML files without getting errors like these (all from the project InteractionGallery-WPF):
Content\PannableContentScreen\WorldMap.xaml, line 3, column 9: "Uri is not supported in a Windows Presentation Foundation (WPF) project."
Content\ArticleScreen\Article1.xaml, line 5: "The property "ImageUris" does not have an accessible setter."
Content\ArticleScreen\Article1.xaml, line 7: "The property "Paragraphs" can only be set once."
Content\MainWindow.xaml, line 20: "Type Microsoft.Expression.WpfPlatform.InstanceBuilders.WindowInstance does not support event: Closed"
So, a pretty frustrating first couple of hours with it so far. I did a number of searches already for the text of these errors and could not find anyone else who was having these issues. I should mention that I do not come from a Microsoft background, so my troubleshooting skills are very low in this area - but all the same, I was kind of hoping that the stuff provided by Microsoft would work out of the box so I could break it myself without it coming that way!
Note that it still builds without error, and the application runs fine when debugging. But I'd sure like to be able to use the Design view.
Any ideas?
Do you know how to add references in Visual Studio?. Basically you will need to add reference to Kinect library manually by your self. Search for 'how to' s you will find opening few tabs..
What I did is just a simple step which hope will work for you as well. Click on your article and then in the properties area you will see build action which page automatically. Change that to resource and you won't longer see that error again.
Good luck