We have a VS2010 Beta 2 DSL Project , We can build, deploy and test on our Development machines and all is well i.e When we go to 'Add New Item' we can select our DSL
When it comes to giving the VSIX to someone else to try the ONLY way that they can see the associated Project Item is if they build the DSL Project on their machine, they do not need to F5, it is just a simple Build Solution and then voila they can see it.
Is this a bug or user error?
You might want to update your bits to the RC version, which are now shipping in the VS Visualization & Modeling SDK at http://www.microsoft.com/downloads/details.aspx?FamilyID=cd443b01-d657-4f8b-b5b8-29f1e3e2c424&displaylang=en
This is apparently a known bug
I have found a workaround by adding some guids
{82b43b9b-a64c-4715-b499-d71e9ca2bd60};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}
into the csproj and manually editing the vsixmanifest to add
ItemTemplates
I created a folder called ItemTemplates and then added the generated project item Zip into the folder , I then set the Zip as Content and changed the IncludeInVSIX property to 'True'
Not pretty but it works
Related
I have a solution with over 170 projects in it. I recently needed to add two more projects to this solution. For reasons that are not relevant to this question, the solution is built as at x86.
When I open Configuration Manager, and scroll to my new projects, they say "Any CPU". To change that I select <New...>:
It brings up a dialog to make the new entry. I fill it out like this:
When I select OK, it flashes for a second, then goes back to "Any CPU":
I also tried selecting <Edit...> and I get this:
The Remove button is locked out and I don't have any other options.
How can I get an x86 option setup for my new projects?
I faced a similar problem when I converted C# projects into C# SDK style projects.
I found that after conversion, the project type GUID in the solution file did not change from Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = ... to Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = ....
Solution of this problem in my case was to delete this project from VS solution and add it again. You can also manually edit solution file (.sln) and change wrong project-type-GUID.
In your case, try to check the project type GUID in the solution file and change GUID manually. The list of project type GUIDs can be viewed here.
I'm following this tutorial for setting up an app.config on a Xamarin app.
The Tutorial
one of the last steps is:
Add this PCL app.config file as a linked file on all your platform projects. For android, make sure to set the build action to ‘AndroidAsset’, for UWP set the build action to ‘Content’
Access your setting:
I have no idea what they are taking about, how in Vs2017 do I add a file as a linked file to the sub-os projects?
I'm sure this is stupid simple, but I'm totally missing it. thanks.
I figured it out
Right click on Project, add existing select teh file, on the add dialog the add button has a dropdown, change it to add link.
I need to add a new configuration (additional to Debug and Release) to a Visual Studio Project that has been created with the QT Visual-Studio-add-in.
Problem is that the moc files are not automatically added to the project.
Where does the QT Visual-Studio-add-in store the configuration rules for adding a moc_file based on an existing header file?
If I generate a new configuration like Release_Special
there should be a new filter Release_Special in the project that contains the files
moc_Test1.cpp
moc_Test2.cpp
with correct exclusion rules.
I am using VS2010 and qt 4.8.3.
Thank you and best regards
M.S
Took a while, but I managed to figure it out.
You need to create a new configuration without losing any of the Qt add-in custom-added stuff. Open the Configuration Manager and create a configuration, but be sure to select Debug or Release in the "Copy settings from..." dropdown list. Let's say you named the new configuration "Debug-foo", and used the settings from the pre-existing Debug configuration.
Build the project. All necessary files will be moc'd and the outputs will appear inside the GeneratedFiles\Debug-foo directory (it will be created automatically). The build will then try to process the moc files from the Debug configuration which is clearly not what we want, so as soon as the build finishes moc'ing, you can just terminate it.
Add a new filter, named "Debug-foo" under Generated Files in the solution explorer, then Add->Existing item to that, selecting all moc_(...).cpp files from GeneratedFiles\Debug-foo that the build just created.
Last, but not least, select all the files inside the Generated Files\Debug filter, select Properties and set "Excluded from build" to true, otherwise the build will include moc_ files from both Debug and Debug-foo.
Hopefully, this will be fixed in some new version of the add-in. Maybe it is already, who knows (I encountered this problem with add-in 1.1.10).
As to the part of your question about where the rules for moc_ generation are stored;
creating the configuration as a copy of an existing one saves you the trouble of adding custom build instructions for invoking moc for every file that requires it. These are stored inside the Properties of invidual header files which need moc'ing under "Custom Build tool" if you want to check them out.
I have a project that lives in an SVN repository. The repository is added to Xcode, I can browse it from my Organizer and check out projects. Here's the problem. Whenever I'm trying to update an old version of the project to a new one, I right-click on the project int the Project Navigator and go to Source Control -> Update selected files, I get the following error:
The operation could not be performed because the selection is invalid.
Please verify the selection and try again.
What am I doing wrong? I tried selecting individual files instead of the project, and I tried selected lines of code (silly, but you never know). Am I not checking out the project correctly? Is this a common issue?
Cheers! = )
Go to settings and map Update All and Commit All to some keys, when you use those options (no update/commit specific file but ALL project) you shoudn't see those errors.
Maybe something wasn't done properly in the past and from then on the system cannot manage it anymore correctly.
I would have backuped the probject and then delete the project entire directry, and than checkout the project from scratch using the organizer.
I'm working on an IronPython project on VS2010 and I've notice that for the python project (which is setup as a Console project, but really just contains a number of scripts that are hosted in a C# app), everything that is in the project directory will show up in the VS solution explorer under that project. So, for example, the .svn folder shows up. Which I obviously don't want or need to be there.
Is there any way to tell it to hide specific items? I sure can't find one.
Currently we have a directory based project system - which as you have seen includes all of the files in the project dir. We were planning on having an exclude option but the feedback we've been hearing so far is that we should move to a normal VS project model where you need to explicitly add the files. The next CTP release (which should be out in a week or so) will change to a normal project model.
There does still seem to be some interest in the directory based model so we may bring it back via an option in a future version.
You should be able to just right click the folder, choose "Exclude from Project"
Then, make sure "Show all files" is NOT on at the top, by the solution.