What are these weird shorcut targets for microsoft apps? How do I find the executable file? - location

I'm trying to find the executable for the minecraft launcher so that I can add it to steam to make use of the premade controller setup. Usually this would be easy as I could just go to the file location by right clicking, but I noticed that these new window's apps don't allow you to. I made a desktop shortcut and the target type was this weird code I haven't seen before. Does anyone know what's going on here? in the app store there is no option to go the file location, and I don't remember choosing a drive or install path. I know minecraft is in appdata but I want to know what's going on with this HD lockdown
screenshot of shortcut properties with weird target type

Related

Windows: How to associate developed software with a file type for context menu "open with"?

I'm not a Windows developer and my knowledge of the OS is very limited.
I wanted to write a very simply image viewer software for the Windows OS because such a thing doesn't seem to exist but we have such tools for Linux and they work well.
I am now at the stage where I have something working. But I have no idea how to "install the software program I have written" so that I can associate it with file types such as jpeg and other image files.
I have written this program in C++ although that probably isn't particularly important information.
The point being I am left with an executable file and no idea what to do with it.
I guess the first step to "install" it would be to create a directory in C:\Program Files\ and simply move the file there, although I'm sure I can do some research and figure out how to write an MSI installer to do that.
Where I become stuck is on other things, like how to create a start menu entry. (Desktop shortcut is easy it's just a link, moved to the users Desktop folder?) And then how to get a right click entry for file types such as PNG bmp and jpeg. (So that "open with" "my program" works)
I tried doing an internet search for this kind of thing but really didn't know what to search for. Can anyone offer me any advice on this or point me in the right direction?
Or is this perhaps the kind of thing I would just get an MSI to do everything for me?
For adding a Start Menu entry, you'd need to write a link into C:\ .ProgramData\Microsoft\Windows\Start Menu\Programs.
There you can add just the link to your application or put it in it's own folder. As for the Context Menu entries, there are two options: Adding it manually (But my guess is that you want your installer to do so) by selecting the exe or by modifying the registry.

How to build screen saver in Xcode 4?

I'm making an OSX screen saver in Xcode (Objective-C, ScreenSaverView class, etc.), and it runs within Xcode correctly. When I navigate to the build output folder and double-click on the the .saver file, it opens System Preferences/Desktop & Screen Saver and asks if I want to install it. All correct.
But when I email the .saver file to myself and open it, System Preferences opens but not to Desktop & Screen Saver and no option to install it is presented. I think it may have to do with the fact that when I build it (with, as far as I can tell, build settings specifying "Release" instead of "Debug"), the output file is still in /Users/Me/Library/Developer/Xcode/DerivedData/ScreenSaver/Build/Products/Debug/ rather than a release folder.
What am I missing here? I have very little experience with configuring build settings, compiler flags, etc.
Edit:
For what it's worth, it seems to work if I compress the output .saver file as a .zip and email that instead. Not a great solution though.
As described in the comment above, apparently it's being built correctly; email messes up binary file attachments so to have it work correctly it should be encoded (e.g. by zipping it) before attaching.

WP7 app could not start for debugging

I have to create around 200 WP7 apps that are very similar. They differ only in the content, icons and name. So manually create them isn't a good idea so let's I've written a little tool, which does the following:
Copy the created template project
Copy the content files from a source directory to the copied template.
Change the app name, tile name and app id in the WMAppManifest.xml
Add the copied content files in the .csproj-file.
This works and the generated project opens error-free in Visual Studio 2010 and compiles without errors. The xap-file can be deployed on device and emulator.
The problems:
If I want to debug the app by pressing F5 in Visual Studio I get "The application could not be launched for debugging. Ensure that the target device screen is unlocked and that application is installed", both for device (which is unlocked and connected with Zune/WPConnect) and the emulator.
If I try to start the app on the emulator it closes immediatle after start. BUT if I start the app on my device it works like a charm. Crazy stuff.
The curious stuff: If I do the things which my little tool does manuelly I can debug the project from Visual Studio.
This only occures with my generated projects. Every other WP7 project (existing or newly created within VS) works and debugs error-free.
I tried to PCs: Win7 x64 with VS2010 Ultimate and an other one Win7 x64/VS2010 Pro and on both maschines I have the problem.
Maybe someone has an idea which causes the problem. Thanks for the help!
Edit: I've seen something new: The AssemblyInfo.cs file is located in the properties folder and correctly included in the csproj-file. But if I try to open the Assembly Information from the project properties all fields are empty and if I try to set them I get an error ("value is not in the expected range" or something like this).
I've got similar problem with some sample programs.
It turned out that I have to set in a Solution properties:
Active config => Debug|Windows Phone
it works for me
If they only differ in content, icons, and name, would it be simpler to make one complete app, copy it 199 times, and then just put the appropriate files into the correct directories?(if you made a tool to make templated projects, i'm sure you could do this with code too)
Plus that way if you ever need to change the program you can just recopy with that code again, but not copy the content, thus updating all of your individual 200 apps.

Visual Studio Deployment Project Application Shortcut does not allow drag and drop file opening

I'm having an issue with an creating application shortcut on the desktop from a Visual Studio 2010 deployment project. The shortcut is created just fine, but when I go to drag and drop an application-specific file onto the shortcut, it doesn't work (the cursor turns into the red circle with a slash through it). On the other hand, if I go to the application directory and do this on the executable itself it works fine (it opens the file properly). The interesting part is if I manually create a shortcut to the executable after install, it also works to drag and drop files onto that.
Something that might be useful that I discovered when I was trying to fix this is that if I open up the properties dialog of both the shortcuts (the deployment project created one and the one I made manually), the manually created one has as its target the full path of the executable, whereas the other one just has the name of the executable (although its start in directory is correct). They both run the application when I double-click on them and they both have the correct icon displayed.
How do I get the deployment project created shortcut to allow drag and drop of executable files onto it to open them?
I had the same issue.
First i went here, which answers your question:
http://social.msdn.microsoft.com/Forums/en/vssetup/thread/b57f1d84-9b0c-4c29-b140-0555f92ffed8
But apparently support for orca.exe and WiRunSQL.vbs seems to have disappeared because I couldn't find it on msdn anywhere.
Then i found http://www.instedit.com which seems to have done the trick. I liked the automated answer of the vbs script, but oh well.

How do I Create a link to an executable Installed by Visual Studio Setup Project

I am working on a visual studio setup project. I want the setup project to install the executable for a windows forms project, and then put a link to that executable in the Programs Menu on the target machine. In the Setup Project I clicked 'Add'-> Project Output... and selected the Primary Output from my WindowsForms App. So that should install the program right? Ok, so next I went to the File System on the Target Machine, right clicked on the Primary output from WindowsForms App and said Create Shortcut. I then moved that shortcut into the User's Programs Menu folder.
I tried running the installer and it works ok but for some reason whenever I click shortcut that is in the Programs Menu It actually installs the program before running it every time. Why does it do this? Did I add a shortcut to the wrong thing? If I navigate to the directory application directory and click the .exe file it just opens the program without doing any install. Does anyone know what is going on?
I read somewhere that I could actually make a shortcut in windows explorer that targets my output .exe and then add that file to the installer project but I can't see how that would work on every machine it gets installed on.
I think this is how I did it... been a while tho.
Application Folder
Primary Output From MyProjectName (Active)
Right-Click => Create Shortcut
Then
Users Program Menu
Right Click => Add Folder
Go back to "Application Folder"
Move the shortcut over to the program menu
Rename it to whatever you need. The "Type" should say "shortcut"
Is that kinda what it looks like for you right now? Something in
* User's Program Files
* My App Folder
* Start My Application (shortcut)
And need I say, MS's install projects are a nightmare :) Just open the .VDproj and look. I never thought i'd say I like the csproj xml format, but in comparison...
The problem was not actually in how I was creating my shortcut but rather what the shortcut was pointing too. The executable that the shortcut was targeting was not in the main installation folder and for some reason it didn't like that. Restructuring the install directories a bit fixed it.

Resources