When I right click on a project in my solution and go into the properties, I don't see the Compile tab on the left. I see Application, Build, Build Events and then the next one is Debug.
I've Googled for this but couldn't find anything, and also couldn't find anything here. Does anyone have any idea what I'm doing wrong?
Many thanks!
The Compile tab shows up for Visual Basic projects, but not for C# projects. For Visual Basic it mainly houses constructs specific to VB, like OPTION EXPLICIT, but there are elements like target platform that are found on the Build tab for C#. The target framework, available under the Advanced Compile Options of the Visual Basic Compile tab is found on the C# Application tab.
UPDATE: With Update 2 of Visual Studio 2012 I'm now seeing Target Framework for a VB project also in the Application tab.
Related
I have a VSTO for Excel project with a custom ribbon tab. The solution builds without errors. I can run the solution. It launches Excel and displays the custom ribbon tab and task pane without any issue.
When I try to open the designer for the custom ribbon tab in Visual Studio 2019, I get the following error:
Could not find type 'Microsoft.Office.Tools.Ribbon.RibbonTab'. Please
make sure the assembly that contains this type is referenced. If this
type is a part of a development project, make sure that the project
has been successfully built using the settings for your current
platform or Any CPU.
The solution builds and runs without any issues.
When I expand the error info, There is no stack trace or error line information available for this error.
The build settings are set to 'Any CPU'.
The assemblies that contain 'Microsoft.Office.Tools.Ribbon.RibbonTab' are included in the project references. These are Microsoft.Office.Tools.Common and Microsoft.Office.Tools.Common.v4.0.Utilities.
I have tried to Clean, Rebuild, and Restart Visual Studio 2019. This had no effect.
I could not find anything definitive when I Check Windows Forms Design-Time error list.
Would anyone know how to address this issue so that I can open the custom ribbon in the designer?
Is VSTO still supported by Microsoft? All documentation appears to be several years old.
This is a Visual Studio issue, not a C#/Build/DLL linkage issue.
Make sure your Visual Studio setup (do the Modify in the installer (#1) if already installed) has these two components checked:
Is VSTO still supported by Microsoft?
They are moving to an online office365 addin (my words) type VSTO. As to new features, not recently. One can still put in a Visual Studio support ticket if you have the right subscription.
I have never had any issues with ribbons, but sometimes the winforms res files in designer do not show and I use the JetBrains Rider editor to view those controls when VS fails.
Hi I'm trying to teach myself c++ but I can't even get the most important feature to work. The build/compile button won't show. Its grayed out. I only want to use visual studios because its what all the devs use in my friends company where I want to work. So, any way to get this thing working? This is Visual Studios 2013, I've tried the profile changing feature in attempt to fix it but it still shows up as grayed out and I can't use it. I have made no other changes since installing it.
Also to start my code I did file> new> file> C++ file
Thanks for any help.
Visual Studio relies on projects, so you need for your source file to be part of a project - this would also hold all the configuration for compilation and linker settings, analogous to a *nix style Makefile.
To create a new project, Do File > New > Project... And choose a suitable template from under the Visual C++ section. Typically, if you're just starting out, and only want to work with the console, then you'll probably want to choose "Win32 Console Application" as the project type.
I am developing a Visual Studio Add-in where one of the controls is a settings editor similar to the locals or watch window. Because strings are one of the data types being displayed/supported in this control, I would like to add a text visualizer similar to Visual Studio's baked in visualizers for debugging. I have provided a picture below to illustrate exactly what I'm referring to:
http://imgur.com/fgSFDqw
Am I on my own, or is there a way to reuse the existing Visual Studio debugging visualizers in my project?
thanks :)
These visualizers appear to be tightly coupled to Visual Studio and are not available via any command or interface. If anybody discovers otherwise, I'd love to know :)
I'm looking for a quick overview on how to create a resource-only DLL in Visual Studio 2012. I found this old article for Visual Studio 2005, but that doesn't exactly appear to be relevant anymore:
http://msdn.microsoft.com/en-US/library/24b2tcy0(v=VS.80).aspx
The goal is that I (the graphics guy, not the programmer) can make the resources DLL for the programmer to pull bitmaps and icons from. I can follow instructions, and have enough Visual Studio experience to figure out at least cursory instructions - I'm just looking for a starting point if nothing else.
Thanks in advance,
Beems
Start a new project of "class library" type.
There will be a single class, depending on the language you chose it
will be named differently. Delete it.
Add your resources to the project, change their properties to
"Embedded Resource"
Compile
I'm trying to move a solution I have over to Visual Studio 2012 and one of the project types is .vdproj.
According to this link this project type is not supported in Visual Studio 2012:
MSDN says they recommend that you use InstallShield Limited Edition for Visual Studio.
The problem is, when I open up my solution in VS2012 and try to add a new "Enable InstallShield Limited Edition" project to my solution, I get an error message saying:
Creating project 'test'...project creation failed.
Why might I not be able to add a project of this type to my solution?
If I make a new empty solution I can't make an InstallShield project it in either.
I'm going to try to download InstallShield limited edition and see if it does anything.
I tried out that InstallShield download, and it added two extra project types, but I'm unable to create either of them. I'm able to add normal website projects to my solutions just fine, but not deployment projects.
The installer was named the same, but this one prompted me to re-start. After re-starting I was able to add an InstallShield project, but it gets created in its own solution. So, it looks like now I have to figure out how to use it, and I'll be good to go.
It's looking like the limited edition doesn't have support to install Windows services.
This will probably be long and boring because there's lots of steps, but I'd like to write up how to move from a Windows service installer .vdproj to the new InstallShield LE that's available in Visual Studio 2012.
Step 1: Create a merge module (.msm)
Follow the steps of this guide.
Notes:
You will need to install WiX 3.6 and isWiX
The latest release of IsWiX doesn't enable the Tools menu item in Visual Studio 2012. Edit the file: C:\ProgramData\Microsoft\MSEnvShared\AddIns\IsWiXAddin.Addin (XML) and clone the HostApplication element and update 10.0 to 11.0.
In step #8 of the guide, it references a code tab. This has been moved to the XML Editor item in the bottom of the left menu
I left the MergeRedirectFolder empty for my installation
Here is my isWix files view:
After you're done with the guide you should have an empty .wxs file that looks something like this:
Using the Component XML element pulled from here you should end up with a .wxs file that looks like this:
Hit build and you should now have a .msm file.
Step 2: Adding merge module to InstallShield
Go though the wizard to setup the basic install information like company and version information.
Find the redistributables view in ISLE. Right click the list and select browse for module. After your module is found and added, right click the modules and select properties. Set the destination folder drop down to INSTALLDIR. I had to set mine to the lowest level folder I created for my install path, so you might have to experiment a bit.
Build Project, and test on virtual machine
Redistributables Screen
If you're getting errors about the path being too long you might need to change the release location to something close to the root.
Here's a list of all the build errors for reference.
Now you should be able to run your installer and have it install/start a Windows service. A lot more work than .MSI files, we got it to generate in Visual Studio 2010, but overall it was not too bad.
While there is no easy or truly supported solution for Visual Studio 2012, Visual Studio 2013 users can get an extension from Microsoft in the Visual Studio Gallery.
I found this post which says you must download InstallShield first. It's a very confusing way to work. I suggest to vote up the post on the connect site and give them comments letting know how poor that is. They could at least give a more descriptive error http://connect.microsoft.com/VisualStudio/feedback/details/732196/project-creation-failed-for-installshield-limited-edition#tabs