I have a .net project that has a post build event to apply a signature to the final assembly. But InstallShield is not getting the signed assembly. Does anyone know why this is happening?
The limited edition is removing the digital signature.
IF you want the exe to be signed you need to have paid version and select "Include files and patterns" of the signing tab.
Related
For some reason(about the digital signature of the desktop bridge app, see here), I can't use visual studio to package my project. Makeappx seems to be able to do this, but those commands are too complex for me. Is there an easier way to achieve this?
Or to put it another way, how can I directly refer to the EXE file (which I can sign) rather than just the project in the application package project?
If Visual Studio is too complicated I recommend you get the free Express edition from Advanced Installer.
In the link include you can find a video that shows how to build an MSIX package (for bundle just change the radio button option from Builds page).
Additional info -
Publishing an MSIX package in the MS store.
Disclaimer: I work on the team building Advanced Installer.
I have a native Win32 project written in C and wanted to visualize my project's dependencies from external DLLs. Visual Studio 2012 and 2013 let me generate a code map which would not only show all my functions and their dependencies from each other using arrows, but also all external libraries I used, which functions I used from those and which of my functions called which external functions etc..
Now, in Visual Studio 2015, this latter part seems to be missing. I can not get Visual Studio to show my project's external dependencies. I only see the internal ones. So here's my questions: Am I missing something? Do I have to activate a specific option in my project settings? Or are those external dependencies just not working in Visual Studio 2015 right now?
Steps to reproduce: Create a new non-empty Win32-project. In the Architecture menu, select Generate code map for solution. You will only see Win32Project1.exe in the middle of the screen. Meanwhile, Visual C# seems to be fine, showing the external dependencies. Create any C#-project for comparison.
Thank you for taking the time to post this! This looks like a regression, as in Visual Studio 2013 an Externals group with external dependencies is shown for C++.
I've logged a bug on Microsoft Connect so that you're able to track this externally:
https://connect.microsoft.com/VisualStudio/feedback/details/1694695
I have posted this workaround on the link that Bogdan Gavril listed and hope it helps someone. Unfortunately, it requires that you enable "CLR" support for your project. Basically, it appears that the VC++ linker and librarian is looking for a flag that indicates some type of managed code. At the very least, the code map is dependent on the mscorlib.dll reference injection. To make the CLR issue (which adds a lot of unnecessary bulk for native code) less a problem, simply create a new build configuration for use only when you need code maps with external dependencies. Make sure you've selected "CLR Support" on the general options of the project properties configuration page. Then, clean (probably not necessary) your solution and generate a code map. You will find the external dependencies as expected!
Zac
How to package VC++ Redistributable runtime library (for Visual Studio 2013 available here) into a cab file that should get downloaded automatically only if needed on the client machine?
The sample packaging given at msdn doesn't help as they have not made mfc120.cab available at the similar url, the way they did for mfc42 as in their sample.
As a workaround (which works) I have created a cab (vcredist_x86.cab) out of the vcredist_x86.exe and invoking it only if any of the dependent runtime libraries are not available. But I believe there could be a direct way of doing things instead of going this odd way.
Here is the inf (inspired by the msdn sample):
[version]
signature="$CHICAGO$"
AdvancedINF=2.0
[Add.Code]
myModule.ocx=myModule.ocx
mfc120u.dll=mfc120u.dll
msvcr120.dll=msvcr120.dll
msvcp120.dll=msvcp120.dll
[myModule.ocx]
file-win32-x86=thiscab
clsid={C4B5FFD0-6DE6-D47E-A9B1-5CF1D3EE869C}
FileVersion=1.5.0.12
RegisterServer=yes
[mfc120u.dll]
FileVersion=12,00,21005,1
hook=mfc120installer
[msvcr120.dll]
FileVersion=12,00,21005,1
hook=mfc120installer
[msvcp120.dll]
FileVersion=12,00,21005,1
hook=mfc120installer
[mfc120installer]
file-win32-x86=vcredist_x86.cab
run=%EXTRACT_DIR%\vcredist_x86.exe \Q
It would be great to know the right way of packaging this particular version of VS 2013 - similar to the sample given. I don't want to copy the vcredist_x86.exe or the dlls at the server, so that it works fine as given in the msdn sample.
I have problems with my InstallShield projects, that are using InstallerClasses, during the Major Upgrade. The setup is calling the old version InstallerClass or just throws error 1001.
I decided to use the DTF technology, but I am unable to link the generated *.CA.dll file to the "DLL Filekey" property. I am linking the project as a "primary output".
Any idea how can I use the DTF custom action project and link it to Basic MSI Installshield 2012 project? I want to avoid referencing the CA file directly because I am creating automated builds.
Many thanks,
Marek
I saw this SO question asking for a PDF viewer for MonoTouch, which is just what I need. First I tried the Xamarin code sample suggested by poupou, but this needs a lot of extra work to use. So I decided to try the mTouch-PDFViewer suggested by Alex.
So I went to the download page and on to the GitHub for this component and cloned the repository. The problem is that the Visual Studio solution opens with a message saying I need a different license for Xamarin than I have. I only have a Xamarin Indie license and am therefore not able to build this library.
Is there a way around this? If I copied all the code into the Xamarin Studio, would it work then or can't I use this component at all due to licensing problems? Will it work in the app as long as I get hold of the dll file or do I need the more expensive license?
I have sent an email to the support email address for the mTouch-PDFViewer asking if the dll is available somewhere, but I was wondering in general if the licensing limits the use of dlls or just the ability to compile the code.
Indie license does not have Visual Studio support. An Indie license requires you to use Xamarin Studio on a Mac. There should not be any restrictions on using specific components.
Also, for basic PDF viewing, iOS has excellent built in support, which you might try before using a 3rd party component.