How to create xap file not exe? - visual-studio-2013

My program automatically generates an appsturio.exe file but I need to be .xap.

EXE is a binary executable.
XAP is an XML-based declarative framework for installing Ajax web applications.
You can't covert between the two you would have to decomplie the EXE and then rewrite it as a Ajax application.

Related

How to package .NET application for veracode scanning

I am using VeraCode for the first time. I have ASP.NET MVC application .NET 4.7.2. To analyze ASP.NET applications, Veracode requires you to supply all the forms the application uses and all the dependencies in the compiled form, which are the DLL, EXE, and PDB files.
I used VeraCode's Veracode Static for Visual Studio extension to build application using VeraCode settings. I could upload application for scanning directly using Veracode Extension menu. However this extension uploads one file at a time and extension is very buggy. Every now and then upload just stops in the middle and I have to start all over again.
What's the best way to package DLL,PDB, JS files. By default The compiled assets are deployed in \PrecompiledWeb folder
1> Can I zip of the entire folder \PrecompiledWeb and upload for scanning? This folder will have other assets as well, like .json, web.config files.
2> Or Do I manually need to create zip of (DLL & PDB) and another zip of only JS files
3> Do I also need to include .compiled files?
Yes you can zip the file. It uploads faster. Its okay to have other
assets there, If Veracode supports it, it will scan it.
No, One zip is fine for all files.
No. '.compiled' is not mentioned on there help page. This says:
Applications must be packaged as EXE, DLL, NUPKG, or ZIP files. Veracode requires debug symbols (PDB files) to be included with the application to accurately report the filenames and line numbers for findings.
And for JS files. See this.
I have done a scan with exe, dll, pdb, js, css, html all in one zip. It works.

GetVersionEx function for Windows 8.1 and upper (fasm)

I am writting application in fasm and have problem with determinating Windows version 8.1 and upper. Functions GetVersionEx and Version Helper give me Windows 8. As MSDN says, I must target my application via changing manifest file in Visual Studio, but I'm not using VS, so what should I do?
Any programming environment that allows you to link resources into the compiled executable can be used to create a manifest resource. All you have to do is write a suitable .manifest file for your app that contains the desired XML values, and then link that file's content directly into your application's resources, making sure the resource type is 24 and the resource ID is 1, 2, or 3 (see this page for details about when to use which ID). You are not required to use VisualStudio for this.
If, for some reason, you cannot link the manifest directly into your app's resources, you can alternatively save the XML into a file named <myappname>.exe.manifest (where <myappname> is the actual name of your EXE file) and put it in the same folder as your app. This is not the preferred approach to manifestation, but it does work.
That being said, there are alternative APIs you can use instead of GetVersion/Ex() or VerifyVersionInfo()-based helpers to get the correct OS version without dealing with manifestation at all. Namely, RtlGetVersion(), NetServerGetInfo(), and NetWkstaGetInfo() can be used instead (and all of them have been tested as working in Windows 8.1 and 10).
The manifest file is XML file embedded as Win32 resource. It can also be external file with the name your.exe.manifest. Search for examples in internet for sample contents.

Deploy .Exe via Web

I've an HTML5 application packaged into OpenFin environment. The complete package is inside an .Exe executable that we wish to ship to end users.
We tried to create a link to the executable that could be downloaded from a web link - but seems most of the company' security permissions environments/firewalls block .Exe file downloads.
Our requirement is to ship the .EXE file (we do not have certain files - so may not be able to effectively create a clickonce deployment package)
Is there a better way, even using ClickOnce to ship the .Exe via web url?
You can wrap exe into a zip and can ship..

Expose setup in what file format: zip, exe,..?

this may be a stupid question... but I have created a setup.exe using Installshield that installs my application. I cannot use an MSI because I want to include prerequisites, like for example .NET 4.0 framework web install.
So, I put this setup.exe on my web site somewhere, but when I try to download this I get 'The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server.' Obviously a security is going on that makes it impossible to download executables.
So I zip it to setup.zip, and now it can be downloaded.
My question is: what is the best way to distribute such a setup via the web? Is it acceptable to make it a zip file for users to download (because then they have to unzip it first), or should I just allow an executable to be downloaded?
I've seen this practice for some products and it's always annoying. Why would you give me a ZIP file which contains a setup file? There are no advantages, but a lot of disadvantages:
I need to perform an extra step to extract the ZIP
I need twice the disk space (the ZIP plus what's inside it)
Most users don't see a ZIP file as an installer, they are used to "setup.exe" or "setup.msi"
The correct approaches are:
configure your website to allow EXE file downloads
or
distribute a ZIP which contains your application files (instead of using a setup file)

NSIS - rebuilding the installer exe file

Suppose I have created an installation exe using NSIS. The exe is a compressed (7zip maybe) file that contains everything to install the application on a fresh machine, and that comprises big exe files (like .NET runtimes, mysql server installer, etc.). I have to send via the Internet the big exe file to another person.
To save time and bandwidth, I'd like to remove the contained big files; I can do that using 7zip to open and extract all the files in the original exe, delete the big ones, rezip using again 7zip. This works up now.
The other party will download the reduced zipped file, but then has to reintroduce the big files in some way, recreating the exe installer.
I don't know how to achieve that. I've tried with paquet builder with no success.
Is that possible?
I don't think it's possible. But I think I have another solution for you. Why don't you simply execute separate executables (like .NET runtime etc) from NSIS bundle? This way you don't need to include them into resulting bundle. Just tell the user to download them and put the into proper place. It would be easier than instructing them to assemble bundle from pieces, no?

Resources