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.
Related
I have 4 files in my Xamarin.Forms project that reside in a folder named MiscFiles. The build action for each is set to Content and Copy to Output is set to CopyAlways. The first 2 files are database files that have a ".db" extension. The other 2 files are resource files named StaticResources.Resources.resources and TestClient.Resources.resources.
The files are being used by a .Net Standard library which is referenced by the Xamarin.Forms project and also a separate WinForms project. The Xamarin.Forms projects just need to deploy the files with the app and pass the file path to the Standard Library.
I was expecting that when the projects are built that all 4 files would be copied to the Environment.SpecialFolder.LocalApplicationData path which on iOS resolves to:
/Users/me/Library/Developer/CoreSimulator/Devices/A1415D63-CE56-4AA2-B8FB-B89B498E70AE/data/Containers/Data/Application/0682337D-1832-4640-8A90-2DFC525901DD/Documents/
The db files are always present in the Documents folder but the resources files never show up. Are the resource files just not being copied or are they being copied to a different folder? Does Xamarin treat the resources files differently somehow?
I have a build definition, which uploads artifacts (loads of css, js, aspx, dll files etc.) and is working as expected.
I now try to configure a release definition with the AzureRM Web App Deployment step to deploy this to a web app.
The web app already exists and I can deploy to it easily directly from Visual Studio.
In the step I have filled in the following fields:
AzureRM Subscription (appears as expected in the dropdown)
Web App Name (appears as expected in the dropdown)
Package - I want to include all files, so I've set it to $(System.DefaultWorkingDirectory)/MyBuildDefinition/**/.
SetParameter File - left blank
When I try to run the deployment the process finds the first file matching the flag and then fails with the following messages:
2016-08-31T16:01:37.7827094Z msdeploy.exe is located at 'C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe'
2016-08-31T16:01:37.7867084Z filePath = Find-Files -SearchPattern C:\a\r1\a/MyBuildDefinition/**/.
2016-08-31T16:01:38.3277086Z filePath = C:\a\r1\a\MyBuildDefinition\Web\App\app\build\css\brand-style.css
2016-08-31T16:01:38.5537092Z ##[error]Cannot process argument transformation on parameter 'files'. Cannot convert value to type System.String.
2016-08-31T16:01:38.5907083Z ##[section]Finishing: Deploy web app
I am using an OOTB hosted build server.
I also tried running this with Package field set to a zip file, which I created for testing, but this didn't work either.
How can I take advantage of this step in my scenario?
Can this consume non-zip files?, if it has to be zip then how do I generate it from my artifacts?
Ok, got it.
It can't be just a normal zip file. It has to be a zip file generated using MSBuild.
Using websphere 8.5. I am trying to use Monitored Directory deployment and use a deployment properties file using this guide
I have enabled the monitored deploy in the global settings. I have also extracted the properties file using wsadmin and verified that it contains the correct configuration (eg. path to a shared library).
I have put the myconfig.properties file in:
C:\websphere\myserver\monitoredDeployableApps\deploymentProperties
I then drag my application test-ear-app.ear (an ear file containing a war file) into:
C:\websphere\myserver\monitoredDeployableApps\servers\my_server
As a result the app is automatically loaded but the myconfig.properties is NOT loaded and hence I need to manually specify the shared library afterwards.
Any ideas why the myconfig.properties is not loaded?
Actually when you deploy using property file you don't drag ear to monitored directory, but just the property file. So in your case you should just drag myconfig.properties to the monitoredDeployableApps/deploymentProperties directory. In your config file you have to define location of your ear by EarFileLocation=/temp/yourApp.ear it will be automatically loaded and installed in proper scope defined by the TargetServer/TargetServer/TargetCluster properties.
See detailed description in page Installing enterprise application files by adding properties files to a monitored directory
As I read, I think the procedure is the opposite of what you were currently doing : drop the Ear first and then start the install process with the props file.
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.
If I use the publish feature in VS2008 (I think it's called ClickOnce install), and then install the published application in another computer, where are the files copied?
In other words: If I need an auxiliary file (a .txt file) in the same path of the assembly, where do I have to create it?
Thank you.
You should have specified the location when you published the application. Just note down that folder.
If you run the wizard again for the same project it should have remembered the location and the folder will be pre-filled on the form.
I've used this and I specified a location on my hard drive for the Publishing Folder Location. This folder contains the following files:
publish.htm
setup.exe
[application].application
It also contains a folder called Application Files which contains the files needed to build the installation - the exe, the manifest, other dlls and external resources.
I then copy the three files and the folder to the web location specified by the Installation Folder URL.
If you're talking about where the files get installed to then they're in:
C:\Documents and Settings\[user]\Local Settings\Apps\2.0\H165QZM1.QBE\0OAEZTRX.Y3N\[some truncated version of the exe name followed by a GUID]
Which isn't the most obvious place. I should also point out that the folders H165QZM1.QBE and 0OAEZTRX.Y3N will probably be different on different machines, but the only other folder under C:\Documents and Settings\[user]\Local Settings\Apps\2.0 is called Data so they should be easy to spot.
Is the application available offline or online only? My experience is online only and in that case I believe it installs into a temp directory. Can you include your auxiliary file as part of the application files? This may help as well it talks about including data files which can be of any type.
http://msdn.microsoft.com/en-us/library/d8saf4wy.aspx
http://msdn.microsoft.com/en-us/library/6fehc36e.aspx