When you publish a website you get xml files of type .compiled. It contains for example:
<?xml version="1.0" encoding="utf-8"?>
<preserve resultType="6" virtualPath="/App_Code/" hash="ffffffffc89f22d3" filehash="" flags="140000" assembly="App_Code" />
What are those files for? Should a deploy them to the server?
According to the MSDN article:
For executable files in an ASP.NET Web application, the compiler assemblies and files with the .compiled file name extension. The assembly name is generated by the compiler. The .compiled file does not contain executable code. Instead, it contains only the information that ASP.NET needs to find the appropriate assembly.
After the precompiled application is deployed, ASP.NET uses the assemblies in the Bin folder to process requests. The precompilation output includes .aspx or .asmx files as placeholders for pages. The placeholder files contain no code. They exist only to provide a way to invoke ASP.NET for a specific page request and so that file permissions can be set to restrict access to the pages.
Related
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.
I have a .net application that currently has resource files for all it's content, one per .aspx and .ascx. Currently there are only resource files for english.
I now need to add resource files for another language which means I need to replicate all the resource files with just the keys and no values, files named with the correct culture extension eg es for spainish.
My application is built against the .net 3.5 framework in VS2008.
Is there any way of automatically creating/generating the new resource files, in the format detailed above for the entire solution?
You could use this free command line tool or a more sophisticated service like Amanuens.
Disclaimer: I've built the tool and my company is behind the service I've linked.
What are all the files will be created when we publish the vb.net application
and functionality of each files
From: http://msdn.microsoft.com/en-us/library/ff699352.aspx
For any ClickOnce publication, the chain of dependencies includes the
following:
A deployment manifest that points to itself or to another deployment
manifest through the embedded deployment provider URL. (ClickOnce
supports a one-hop redirect through this URL.) A deployment manifest
that points to the application manifest through an embedded code base
URL. An application manifest that contains relative paths to each of
the application files. These files must reside in the same folder or a
subfolder in which the application manifest resides. The application
files themselves, usually with a .deploy file name extension appended
to the file name to simplify mapping these files to MIME types on the
deployment server. ClickOnce automatically strips off the .deploy file
name extension on the client side after the file is downloaded.
I've been told to create a 'manifest' to achieve Reg-Free-Com between a VB6 .EXE and a .NET DLL.
What is a 'manifest' in this context?
What does it mean to 'embed' a manifest?
From: http://msdn.microsoft.com/en-us/library/ms973913.aspx#rfacomwalk_topic2
Registration-free COM uses manifest to refer to text files with the .manifest extension containing XML, which either defines the identity of an assembly (assembly manifest), together with the binding and activation details of its classes, or defines the identity of an application (application manifest), together with one or more assembly identity references.
To 'embed' a manifest means the text information is embedded in the dll as a Win32 resource rather than sitting on disk as a standalone text file.
I use ILMerge to merge several of my C# project DLLs into a single DLL for the whole solution. I have each project produce a .XML file of its documentation for Intellisense, and I'm having trouble getting those comments to show up when I try to use my merged DLL as a reference in another solution. I have these files all in the same directory:
MergedProjectDlls.dll
Project1.XML
Project2.XML
Project3.XML
Project4.XML
I tried renaming a single project XML file to be MergedProjectDlls.XML then removing and re-adding the reference in Visual Studio, but Intellisense still wasn't picking up on the comments that I know are there in the project XML file I renamed.
I was hoping to somehow merge all these project XML files into one titled MergedProjectDlls.XML anyway. Is that possible? Would Intellisense then pick up on it automatically when it's in the same directory as MergedProjectDlls.dll?
Edit: just found this on MSDN:
To use the generated .xml file for use with the IntelliSense feature, let the file name of the .xml file be the same as the assembly you want to support and then make sure the .xml file is in the same directory as the assembly. Thus, when the assembly is referenced in the Visual Studio project, the .xml file is found as well.
And also:
Unless you compile with /target:module, file will contain tags specifying the name of the file containing the assembly manifest for the output file of the compilation."
Der, it turns out that's just a command-line option to ILMerge:
ILMerge.exe /out:MergedProjectDlls.dll
Project1.dll Project2.dll Project3.dll
Project4.dll /ndebug /xmldocs