You need to ensure that enough debugging information is available for MyApp…

You are developing an application that produces an executable named MyApp.exe and an assembly
named MyApp.dll.
The application will be sold to several customers.
You need to ensure that enough debugging information is available for MyApp.exe, so that if the
application throws an error in a customer’s environment, you can debug the error in your own
development environment.
What should you do?

You are developing an application that produces an executable named MyApp.exe and an assembly
named MyApp.dll.
The application will be sold to several customers.
You need to ensure that enough debugging information is available for MyApp.exe, so that if the
application throws an error in a customer’s environment, you can debug the error in your own
development environment.
What should you do?

A.
Digitally sign MyApp.dll.

B.
Produce program database (PDB) information when you compile the code.

C.
Compile MyApp.exe by using the /unsafe compiler option.

D.
Initializes a new instance of the AssemblyDelaySignAttribute class in the MyApp.dll constructor.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


Najlepszy Programista Swiata DAGO

Najlepszy Programista Swiata DAGO

B

Lord Vader

Lord Vader

when you build a debug release. vs creates a program database file that contains debugging info about the program. the debugger uses this info to let you debug the application.

if u create a compiled exe you can still debug it if you have the correct pdb file available. not that the pdb file is tied to a specific build and will let u debug only that particular build. due to the way builds are created a pdb cant debug an exe from a different build even if u havent changed the code.
to debug an exe. place the pdb file in the same directory as the exe. use vs to open the exe and run it.