VB.NET - Hide warning error dll not present - vb.net

is it possible in VB.NET to remove the warning message when the dll is not present in the directory?
DLL Present
DLL NOT Present
I want to save this error in the txt file and I don't want to display the error on the screen when it is not there. it's possible ?

Related

Can't remove reference to template

I have a macro-enabled Word document with a reference to a template in the Project > References section of the VBA/macro editor. I can't delete this reference directly. When I delete it through the Developer panel's Document Template dialog box, the template name in that dialog box reverts to Normal, but the macros' Project > References section still shows the old template.
Behavior: the macros fail with the message
"Compile error: can't find project or library."
The missing template appears to be the source of the complaint, since I can create a dummy file with the same name and location as the missing template and the macros load fine. VBA is not relying on any code in that missing template, either, from what I can see. It's just a missing file that's specifically referenced so the compiler chokes. But I need to circulate this macro-enabled document on its own without requiring users to make a new path and copy a dummy file into it.
I've tried editing the XML within the .docm file to remove the reference, but the template is also referenced in the vbaProject.bin binary file. Hex editing that binary file to remove the reference (replacing it with nulls or a valid path/name of the same length) and re-zipping the structure produced a document that Word recognized as corrupted (also tested re-zipping it without making any changes, to make sure the unzipping/zipping process wasn't causing new problems, and that version opened fine but failed at the same place it always fails: the missing template file). Word produced a recovered version, which shows all the macros listed, but it also shows the reference to the template I'm trying to remove.
Windows 10, Word 365 latest
Help?

Vue.js file error "The file will not be displayed in the editor because it is either binary, very large or uses an unsupported text encoding."

I was working on a Vuejs project. So this morning when I opened the project it wasn't compiling anymore and it was reporting an error in one of the components. When opening the component, this message appeared in the VSCode editor "The file will not be displayed in the editor because it is either binary, very large or uses an unsupported text encoding." Clicking on open anyway appears a lot of code with strange symbols as shown in the image. When I try to open the file in another editor, the same problem also happens, but the symbols change. I would like to know what might have happened and if there is a way to recover my file?
Looks like your file is corrupt. Restore from a backup, or re-pull from git.

Embedding an image as a resource in a FireBreath plugin

While using VS (2010), I used to be able to add an image as a resource simply by going to the Resource view and then: Right click project > Add > Resource > Import.
I even asked a question about how to then load it: Loading an image from a resource embedded in a dll, but that changed for some reason.
Now when I try the same thing and save the .rc file, I get this message:
"The resource script FILE_PATH.rc was not created using Microsoft
Visual Studio. Comments, macros, preprocessor directives, and
conditionally included information may be modified and/or removed from
this file during the build process. Replace existing file?"
Even if I click "yes" (in order to just test things) then I get all kind of error messages at compile time:
ResourceCompile:
gen\firebreathWin.rc(8): error RC2144: PRIMARY
LANGUAGE ID not a number
gen\firebreathWin.rc(16): error RC2135: file not found VS_VERSION_INFO
etc...
I have two questions:
What is the correct way to add an image resource which will be added to the compiled plugin using CMake? I searched about it and couldn't find any helping information.
What can be the cause for this change in behavior? since I was able to use the same exact steps before and it worked.
Thanks.
First of all, I wouldn't do this; instead, I'd just put the file in the same directory as your DLL and use the path of DLL to find it.
That said, the "correct" way to do this would be to see what changes are made to the .rc file when you add it in the IDE, copy the .rc file from gen_templates/ in the root of the firebreath directory into your project, and then make those changes to your copy of the file. Any changes you make to the generated file will be overridden any time cmake is run again, which can happen any time your cmake files (CMakeLists.txt, *.cmake) change.

Open and edit DWG file without AutoCAD

I am trying to open a DWG file in VB.NET forms without opening AutoCAD. However, a problem occurs:
The specified module could not be found. (Exception from HRESULT: 0x8007007E)
I also want to edit the image in the DWG file, i.e. most probably a factory layout, and store information about the object used in the layout to figure out the best possible way to reach from source to destination.
This factory layout map is input for a robot which will move according the path available.
Can anybody help? How should I proceed?
Use Teigha or a special program (I don't remember the name) from AutoCad developers to open a dwg file.

Associate file type/extension to non document based cocoa application

This is for some reason really hard to find and solve. Cannot find any documentation on it.
I've got a non-document based application which I would like to open all specific file types, but I do not want to use NSDocuments but let my code handle the opening of file and processing of it. I've added the CFBundleTypeExtensions and all, settings to the info.plist.
Now the application will open the filetype but display an error like: "The document xxxx could not be opened. Application cannot open files in the yyyyy format."
Have you implemented -application:openFile: in an app delegate? If not, your application has no way of knowing how to open some random file in some random format. It's up to you to add that functionality and respond with success or failure.