Visual Studio 2013 VB Program Not Showing Image - vb.net

I have designed a calculator-like app using mahapps metro in VB. It works perfectly. I added both a .jpg and .png image to my Resources file, and add it within my xaml file, and it shows perfectly. Though when I press the "Start" button to test my program – it doesn't show the image in the app. I've read on here that if I change the build state to Resources, then it should appear. Though when I do that, I get some permission access error. Not sure where to go from here.

The original poster said:
I fixed it with uninstalling Visual Studio 2013, and installing it again. Likewise, in Resources folder -- I found my image, and set that build action to Resources, and it showed up on the debug/release build. I left the MainWindow.xaml to Page as a build action.

Related

How can I share an installer generated by Visual Studio?

I made a simple checklist desktop app in Visual Studio 2015, and I'm ready to share it with the world. Problem is that I don't know how to make an installer for it that I can share online. I have an installer exported, but it is Visual Studio's default ClickOnce installer, which won't work when I remove it from its original location
Is there a way I can package it so I can upload it somewhere and then share it? Do I need to code my own, or there some add-in or tool that will do it for me?
Once you have the installer extension this should help you to get started, as the name implies:
https://www.simple-talk.com/dotnet/visual-studio/getting-started-with-setup-projects/
Have a look at this older post of mine:
What you can do,open the project as if going to edit it, just go to "Project" then "Publish(Whatever-your-work's-name-is).vb at the bottom. Then use the wizard to finish. At the end, say you saved your exe on the desktop, three files will appear.
"Whatever-your-work's-name-is".exe And its icon shape varies.
A folder called "Application Files"
And a "setup.exe" Its icon a like a CD on something.
For the first time, click on setup.exe and open the app. From then on, the "Whatever-your-work's-name-is".exe will open normally. I usually store all three on a zipped folder, which I upload on my website and can be downloaded from there.
To get a better example, vist my website.
I use this website to store my files for backup.
You can get the MS Installer extension from here... There's one for VS 2013 too.
(Credit to peterG for commenting this)

Why does Visual Studio start when opening a WindowsApplication.exe file?

I have a VStudio2012 solution for a Windows form app that has been compiled and runs fine for me when I launch it from myproject\bin\debug\utility.exe (the mainform comes up fine and the program runs fine).
I am trying to get a colleague familiar with the program and when he creates a shortcut to the above program and opens the utility.exe by doubleclicking it, then VStudio comes up instead of the mainform of the app.
Is there any way to achieve this without getting into some deployment scenario? I would like to leave this utility.exe where it is now and just get somebody else to run it from there? Is this possible?
Your friend is opening the .config file, not the .exe.
See "hide extensions for known file types"

Why does Visual Studio open decoratedxaml in debug folder than opening my actual xaml when there is a syntax error failing the build

I have a Windows Universal App. I use Visual Studio 2013 Update 2
If I have made syntactical mistakes or used a converter without declaring it's namespace at the top, VS points out errors when trying to build as usual.
But when I click on the error to Navigate to the line that is causing the error.
Instead of opening my actual xaml page residing \Pages, it opens the xaml page in \obj\x86\Debug\decoratedxaml\Pages
However this is not consistent, for some errors it opens the actual file and the decoratedxaml for some others.
This causes problems like me trying to edit the decoratedxaml by mistake and when trying to build again, the build fails and decoratedxaml will be modified to the previous version by Visual Studio.
Is this expected behavior?
Also is there a setting which I can enable so that it will always open the actual file.
I would be glad if someone can guide me in the right direction.
Thanks in Advance.

Visual Studio 2012 - Custom prerequisites are not appearing in the Properties > Prerequisites dialog box

I've created my first Office Add-in using Visual Studio. It targets the 4.0 .Net framework and was created using the new VS 2012. I need to distribute/install this project on various 32-bit XP and 64-bit Windows 7 computers around the office. So I configured the project to be installed on XP (which was my first speed bump because I didn't realize VS 2012 needed an update in order to make a solution that was XP compatible). Now that I have a valid win32 application, I am getting another error:
The following error occurred attempting to install 'C:\filepath...\Import Contacts.vsto':
"No application is associated with the specified file for this operation."
After doing some digging, I think I need to install the Microsoft Visual Studio Tools for Office Runtime on the client computer. To do this, I would like to use the prerequisites properties for the project. So I read up on creating custom prerequisites using some noteworthy sites (e.g, Creating Bootstrapper Packages, Application Deployment Prerequisites, Adding Custom Prerequisites, and Creating a Bootstrapper package for Office 2013 in Visual Studio 2012). I created the files according to that last URL (even though I'm not sure it pertains to the package I need just yet), but it is not appearing in the dialog box under Project > Properties > Publish > Prerequisites
If you read the article, it says the VS prerequisites dialog box should automatically update once I restart VS 2012, which I did but to no avail. I know I'll need to use this feature again in the future, so I would really like to know what I'm doing wrong and fix this. Please help! And I promise to quickly give the ACCEPT to whoever helps me fix this problem! Thank you in advance.
I didn't have any problems following the directions given in the web page and got the bootstrapper added to the Prerequisites dialog. However, there are plenty of possible ways to get it wrong. Some possibilities:
Triple-check the folder you added these files to. Be sure that you picked Program Files (x86) on a 64-bit version of Windows and not Program Files. And be sure that you now see the added VSTOR40 folder along with the other existing bootstrapper folders, like ReportViewer and VBPowerPacks.
You do not have write permission to this folder, UAC prevents copying files there. Be sure that you managed to copy them from, say, an elevated command prompt. Right-click the Command Prompt shortcut and click "Run as Administrator".
If you created the .xml files with Notepad then make sure you didn't accidentally saved them with the .txt extension. If necessary, put Explorer in "programmer mode" so you can see the filename extensions. Control Panel + Folder Options, View tab, untick the "Hide extensions for known file types" checkbox. If you now see product.xml.txt then rename the file to product.xml, same for package.xml.txt
If you created the .xml files with Notepad then be sure to save the file in UTF-8 encoding. File + Save As, Encoding combobox.
For all those who still may face similar issue I think that I found the cause of this issue. It seems that copying folder with custom bootstrapper package (and all necessary files in it) does not "refreshes" the list of available packages. Only when i went through this walkthrough and manually created folder in %Programfiles%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\ for sample package from this walkthrough my package has shown

Intellisense stops working in VWD 2010

I'm working with VWD2010 and as stated in the topic title I have zero intellisense usability for my project.
I installed VWD2010 fresh a few months ago to start and noticed that intellisense wasn't working. For the last three months I was working with VS2010 trial and intellisense was working fine. The trial version expired, so now I am back to VWD2010.
Intellisense seems to work for NEW projects, so I created a new project and transferred all my files from the VS2010 project. Intellisense was working fine for a couple of days, but this morning I am back with it not working...
I have checked the following:
Intellisense works for new projects;
Intellisense is switched on in the editor settings;
I have reinstalled VWD2010 several times before without it making the blindest bit of difference;
I have reset settings both via the Options menu and via the command line, again without it making the slightest bit of difference.
Intellisense was definitely working for this project last Thursday evening when I last switched off my computer.
I have googled this issue several times and can't find the slightest bit of info on how intellisense is actually supposed to work. Advice generally resumes to "reinstall VWD" or "reset your settings"... Any help would be greatly appreciated.
Here is a distillation of some solutions that have worked for other users from the MSDN forum thread IntelliSense stopped working:
In Visual Studio, Go to Tools > Import and Export Settings,
and then select Reset all settings.
After closing Visual Studio, move the .suo file to a temporary
folder, and then reopen Visual Studio.
Check that Build Action property of your source files are set to
Compile rather than Content. Setting a file to Content detaches the source file from the rest of the project, disabling IntelliSense.
If you have a web project, exclude the WebConfig from the project and
rebuild the project. Then include the WebConfig.file again.
If you’re using C++, close Visual Studio, and then delete the .ncb
file. The ncb file contains IntelliSense information for C++. Deleting it resets IntelliSense, but it may take a while to rebuild in the background.
Finally, from the post Visual Studio & XAML – IntelliSense Not Working:
If you're using XAML, adding ;assembly= to the end of the custom CLR namespace fixes the issue.