Original click once update folder location - deployment

I have taken over a click once project from a prior developer. How do I find out where his click once update folder was? The properties of the deployed apps only show where the appdata folder is. I need to know the original update location on the click once server so I can redeploy there, but the location that is stored in the project properties is wrong (as are all of the application configuration values) so I must have an old set of source code.

It's a bit of a shot in the dark, but if you have access to a machine that already has the application installed on it and if the application was configured to check for updates before running, you may be able to see the updates location within the app's CDF-MS file installed on that PC. The CDF-MS file is a binary file but you should be able to use STRINGS.exe or visually inspect it to find the beforeApplicationStartup or deploymentProvider value inside the file.
The file is likely located in C:\Users\USERNAME\AppData\Local\Apps\2.0\RANDOM.STR\RANDOM.STR\manifests

Related

How can I change VS Code Remote Server's default download folder?

I often download file from vscode remote server, but how could I change default download folder? It always opens a specific folder I don't want to download into.
I don't know about configuring the detault download directory, but there was an issue created and resolved to get VS Code to Remember target directory when downloading files #140358, which was implemented in commit ca936dc.
bpasero (one of the VS Code maintainers) commented to close that issue as resolved:
For the "Download" command we now remember the path where to download and restore that. This information is stored globally (i.e. applies to all windows) but will not roam via settings sync, because paths are typically machine local.
Previously we did a questionable computation of a default path that typically always ended up in the user home directory, which imho does not make a lot of sense for the download operation.
Verification:
connect desktop to any remote
right click from the explorer "Download"
pick a destination
repeat and verify the destination restores even across restarts

How to automatically scan the re-uploaded files with some modification in the wildfly-10 without the server restart?

I am using wildfly-10 server. I am providing an option to Upload images or jsp files for the user in the UI and the user can make use of these files in the other section of the application later.
At any one point of time I am allowing only one entry with a particular name. If the user tries to upload file with a name that is already existing then I am trying to overwrite the existing one with the new file.
In this scenario I am facing the below problem:
I have uploaded a image with the name image1.png.
Now if I change some other image's name to image1.png and upload it, the new image is not visible until I restart the server.
Looks like the older image has been cached by the server and it is still referring to the cache location. When I restart the server then it refreshes the cache with the new content of the file.
Is there any way that I can immediately see the changes in the UI whenever I re-upload the modified file?
I am using a custom folder to store the uploaded files in my server.
Is there way that I can enable deployment directory scan for this particular directory only?
You don't have to restart the server, a redeploy of the application should work.
You can define another deployment scanner or the directory scanned by the scanner: http://wildscribe.github.io/WildFly/16.0/subsystem/deployment-scanner/scanner/index.html
Another solution would be to create overlays http://wildscribe.github.io/WildFly/16.0/deployment-overlay/index.html .
Thirdly with exploded deployments WildFly already provide the functionality you have developed: https://wildfly.org/news/2017/09/08/Exploded-deployments/ (note that all jboss-cli operations can be called using HTTP rest API)

MATLab Drive Connector fails on startup

Hi,
I have a problem on my Mac OS X 10.11.5 Beta (15F31a), with MATLab R2016a (9.0.0.341360). When I install the MATLab Drive Connector from the website as matlabdrive.mlpkginstall or from the add-ons menu in MATLab itself, it works absolutely fine; it synchronises my files and displays its logo in the menu bar top-right, through which I can access its menu/settings/etc.
However, upon the second start-up of my computer; MATLab Drive Connector is no longer usable. When I open it; an empty menu space is created in my menu items; and when clicking on that space, it's marked as selected; but nothing else happens, nor are my files synchronised. When I have selected the MATLab Drive Connector to start at startup right after its installation, the empty space is immediately created, with the same effects. When MATLab Drive Connector is forcibly stopped via Activity Monitor; the empty space will disappear. I have attached a screen recording [1] of this issue.
The only temporary fix was to deinstall & reinstall the MATLab Drive Connector, after which it worked again,
EDIT:
however since two days, even when attempting to de/re-install, I get the error "The specified key is not present in the current container", as shown in the attached screenshot [2] preventing me from doing anything to fix this issue.
I hope you can provide me with a solution, as the MATLab Drive Connector is very important to me, and I presume this problem also occurs to other users :]
Kind regards,
Isaiah van Hunen
[1] https://drive.google.com/open?id=0B5_0h9k46DFua1NtLU0zZXlnMjA
[2]
If you take a look at the ~/Library/Application Support/com.mathworks.matlabconnector folder on your computer it should contain a folder with the same name as your computer. This folder should contain three folders called locks, logs and services.
The com.mathworks.matlabconnector folder may also contain a second folder with a longer name – probably your computer’s hostname including the domain you are connected to - something like macbook-wifi.example.com - if this folder exists it probably contains a single folder called "start".
If this second folder exists, then I have a solution for you to try:
Move the "start" folder from the second folder into the first folder. This folder should now have four folders: locks, logs, services and start.
Delete the second folder that should now be empty.
Start MATLAB Drive Connector
Now when MATLAB Drive Connector is started it should now find the correct folder and start correctly.
I had a similar issue under Win 10. Typically Connector can be started by clicking its icon in the MATLAB folder in the Start Menu. This however requires a confirmation of User Account Control (UAC). So one needs to eliminate that, so that it doesn't cause an issue on start-up.
Find the folder where the Connector exe is located. For me it was at: C:\ProgramData\MATLAB\SupportPackages\R2016b\bin\win64\MATLABConnector.exe (note that ProgramData is a hidden folder, so make sure you enable hidden files under View in the C: folder).
Next find the Windows start-up programs folder. Hit the "Windows key + R" keyboard combination, then type "shell:startup". The folder should already contain a Connector icon, remove that, or cut & paste it to the Desktop. That icon also required UAC confirmation, so it's no good, we need an icon that doesn't require it.
Follow this tutorial to create another shortcut icon (without UAC) to the MATLABConnector.exe program: http://lifehacker.com/how-to-eliminate-uac-prompts-for-specific-applications-493128966
Once you have your new icon, cut & paste it into the Windows start-up folder you located in step 2.
Exit Connector by right-clicking it in the Taskbar. Then double click the new icon created in steps 3-4. and Connector should start again with no UAC verification step.
Restart your computer, and Connector should start automatically with no problems.

Eclipse local file history

In eclipse, you can right click in a file and then select Team / Show local history. This shows your local saves and is pretty useful.
Now, I made some changes to a file. I am 100% certain I made them. But they have disappeared. Overwritten by someone else I guess. But when I check my local history I can't see my file changes.
My question is:
Does Eclipse always update the local file history for every save? How reliable is it?
Note: I appreciate people are thinking how can someone else overwrite your files. I am working in a force.com project. When you make changes to a file they are push to a central server. There is source control per se. It is like everyone working with a shared folder.
It depends. Each Eclipse plugin dealing with workspace artifacts can optionally set a flag for local history in its API calls to the workspace resource management when deleting or changing files. If the flag is set, changed files surely get copied into local history. But every plugin can set this flag different.
So even if you might have an editor plugin which always uses local history when saving the edited file, another plugin might delete/modify the file without using local history and therefore interfere.
Summary: Local history is not a reliable way to go back to previously saved versions of a file.
If anyone else runs into this issue, check to make sure you didn't accidentally edit a file in a build or target directory. For instance if you are working on a jsp page and make edits, swear you changed it but they are no longer there in the editor or the local history when you open the file, check to make sure you weren't editing the built version by accident.
This sometimes happens if you are quick to use ctrl-shift-R shortcut to open resources. To avoid this, you can set your build or target folder to derived by right clicking on the folder and checking the derived checkbox. This will prevent the resource from showing in the Open Resource view which could save you headaches later.
To get the code back, I opened the target version and used undo to get to the edited version.

ClickOnce and mageUI adding custom file folder problems

What I do: Publishing .Net 3.5 application via VS, or msbuild (whatever), and now I need to insert to the published application separate directory (Modules - not added as a reference to the project - our project architecture does not allow this). So I'm copying the folder to published location then runs mageUI.exe select the application manifest and then the problems starts. As I press the populate button it's adding also hidden directory? So I remove the directory, after I want to save the manifest file I get the
"Warning MSB3110: Assembly 'NAME.Shell.application.deploy' has mismatched identity 'NAME.Shell.application', expected file name: 'NAME.Shell.application.application'".
Did you have the same problems, according to http://smartclient.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=5060 it should be easy as 1-2-3 but it's not.
On the irony side, I am currently updating the SCSF documentation for ClickOnce deployment for .NET 4.0, and now I know exactly what the problem it.
First, you want to publish to a disk location, not directly to the webserver. So do that, and then copy the dll's you want to add to the deployment into the version folder with the application manifest (.manifest). Rename them yourself -- just add .deploy on the end.
Bring up MageUI and open the application manifest in that folder, then uncheck the box that says "add .deploy to the file names". Click "populate".
Then remove the deployment manifest from the list; it's called something like appname.application. You don't want it to be included in the manifest's list of files.
Now you can save and sign the application manifest. Then without exiting mageUI, open the deployment manifest that is in the root folder (NOT the one in the version folder). Click on "Application Reference", then click Select Manifest. Dig down to the application manifest in the version folder that you just signed and select it. Then just save and sign the deployment manifest. It puts a relative path in there, so if you modify the .application file in the version folder, it won't work right when deployed.
Now take that .application file from the root folder and copy it into the version folder (replacing the one that's there) so you have the right copy for that version in case you need it later.
Now copy the whole shebang out to the webserver. it should work.
I think you are saying you need to add a folder of stuff to your ClickOnce deployment? What exactly are you adding? You say modules -- are they going to be compiled in, or is it something else?
If you want to add files to the deployment you have already created, you need to use MageUI to edit the application manifest, which is called something like appname.exe.manifest. (The appname.application is actually called the deployment manifest, which is confusing but true.) After adding the files, you will need to re-sign the deployment manifest as well (assuming you signed it in the first place).
It would be easier just to add what you want included to your project and re-publish. Depending on what it is, you can set the build action to 'content' (jpegs, html, etc) or 'none' (dll's) and then set "copy to output directory" to true, and it will include it in your deployment.
I'm not sure exactly what you are including. Give me more info, and I can provide more specific help.
RobinDotNet