I've opened assembly created by me named CarLibrary.dll with ildasm.exe, but when I try to open it's metadata with shortcut CTRL + M (or by choosing it from the main menu) the program is being closed instead of launching it.
This does work when I try to open let's say mscorlib.dll.
Why is that happening?
I am using MS VS .NET 2013.
I had similar issue.
If you are on Windows 7, try using ildasm in
C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools
I believe this has to do with the .Net framework version of your assembly and the version of ildasm.
i'm puzzled by this problem,I've finally found the path which the assembly you want to opened cannot include non-English character. PLS put the assembly in English character path.try it!
Related
as described in
Delphi 2007 x Windows 10 - Error on opening project
I am looking for the following files as deleted by Windows update
c:\windows\Microsoft.NET\Framework\v2.0.50727\Borland.Common.Targets
c:\windows\Microsoft.NET\Framework\v2.0.50727\Borland.Cpp.Targets
c:\windows\Microsoft.NET\Framework\v2.0.50727\Borland.Delphi.Targets
c:\windows\Microsoft.NET\Framework\v2.0.50727\Borland.Group.Targets
The Windows.old folder is long gone, and I can't find those files in the ProgramData folder.
Can anyone upload and share them?
Thank you,
Fabio
On my reference system, these files are also in this directory:
C:\ProgramData\{B59CE2E6-B15A-4F23-BD0E-72BF2ADDC3C7}\core\7EFD2DA3\6C948720
Others seem to have them there as well.
And they are at https://gist.github.com/anonymous/ab801cd925e5e634518fd5592eb2a46e
I want to change the language of the Delphi XE7 IDE from German to English. BDSSetLang.exe doesn't work for the toolbar and menu items (e.g. 'File / Open project' instead of 'Datei / Projekt öffnen').
Use BDSSetLang.exe in the bindirectory of your Delphi installation.
Did you notice that there are separate settings for the IDE UI and the Library?
QUICKFIX: Move all *.de files from the folder C:\Program Files (x86)\Embarcadero\Studio\15.0\bin\ to another location (so you can move them back if it does not work). If that fixes your issue, delete them.
(Or *.fr for French or *.ja for Japanese- (English is default).
for current versions (Delphi 10.4.2), the solution here works for me:
>cd C:\Program Files (x86)\Embarcadero\Studio\21.0\bin
>bdssetlang en
I have a book with macro and forms in it.
when i open the book a run time error appears and when i look in vba
tools-> reference
Microsoft Windows Common Tools is not referenced and
the reference file path is C:\Windows\SysWow64\MSCOMCTL.OCX
OS: Windows 7 SP 1 32-bit
Microsoft Excel 2010 32-bit
Other info:
The book/file is something I didn't create in my unit, its something i received
Some file work properly but some wont (those file have the same codes inside)
Does anyone knows how to fix this problem? and possible reasons why this occur?
I think this is what solves your problem:
http://social.technet.microsoft.com/Forums/office/en-US/5b241f09-6c76-4320-b302-4cb8224eab7f/controls-from-mscomctlocx-can-no-longer-be-used-in-excel-2010-32bit:
Run CMD under administrator mode
run "REGSVR32 MSCOMCTL.OCX" without the quote
I have a 3rd party .dll that I have successfully added as a reference in both a VS 2010 C# project and an F# VS 2010 project. I can view the contents in the object browser in both cases, but the F# version won't let me "open" the library. It works fine in the C# project (with the "using" directive), and I can write a program that uses the contents of this particular .dll. I have not had any trouble with other .dlls in F#/VS 2010/.NET 4.0 on Windows 7.
Any ideas as to why this might be happening? Or how I could debug this further?
See what the csc.exe and fsc.exe command-lines have for the library in question (in VS, open the 'Output Window' after a rebuild), to see if they both have the same reference (e.g. -r:Path\Library.dll).
And to be clear, you're saying
open NagLibrary
in F# yields the error message in the title, but
using NagLibrary;
in C# works and opens the namespace?
make sure you reference the path within the script using the double "\" convention
for me this worked
#r "C:\homeware\\blp\\api\\APIv3\\DotnetAPI\\v3.4.5.4\\lib\\Bloomberglp.Blpapi.dll"
open Bloomberglp.Blpapi
So I have Visual Studio 2003 running on Windows 7 - yeah I am aware it isn't officially supported - and no, unfortunately I can't change that situation :-(
For the most part it works OK but I have a specific problem, that I can't figure out. The application hangs if you do a project wide search (Ctrl - Shift - F) for a string.
I have a reasonably powerful machine and all the other heavy tasks like compiling and debugging all work fine. It also works if I restrict the search to the current document (Ctrl - F). I am running it as administrator and VS.NET 2003 SP1 has been applied.
The size of the project does not seem to be a problem since a colleague is also experiencing this issue for a single project solution containing 5 pages.
I am currently using Windows Search as a work-around and I was wondering if there is something I missed that I should try.
Try disabling the Aero theme in compatibility. Yeah seriously...
You can do this by right clicking the shortcut to launch VS.NET 2003 and selecting properties, choosing the “Compatibility” sub-tab and then checking “Disable Desktop Compositing” as well as “Disable Visual Themes”
I use Windows 8.1, and the path
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
is invisible and could not be created manually inside regedit.exe.
So I wrote a registry file "abc.reg" with text:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Program Files (x86)\\Microsoft Visual Studio .NET 2003\\Common7\\IDE\\devenv.exe"="^ RUNASADMIN DISABLEDWM DISABLETHEMES"
Execute it by double click icon of "abc.reg" (may be Run As "Administrator").
It works.
(The post is for your convenience in this certain case)
I am running Windows 10 Enterprise 1909 and found global search also causes VS2003 to freeze and stop responding.
The advised registry edit did not work for me - VS2003 refuses to start up when run as admin:
A referral was returned from the server.
This is the same error I get if allowing the compatibility trouble-shooter to apply Windows XP (Service Pack 3).
I can get global search working if I remove RUNASADMIN and DISABLEDWM from the registry value (I.E. leave only DISABLETHEMES in place).
Create a registry key as follows:
Location: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
New: String Value
Name: C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.exe
Value: ^ DISABLETHEMES
You will end up with an even uglier UI (quite an achievement in itself!) but at least global search will now work.