I have a decent handful of property sheet files (.props), here is a short example:
global.props
x86.props
x64.props
app.props
lib.props
It's very tedious to assign all of the correct property sheets to the correct configurations. What I'd like to do is create, for example, app_x86.props which simply references global.props, x86.props, app.props, so that I only have to assign one property sheet to each project configuration.
Is there any way to do this kind of referencing of property sheets?
This is perfectly possible with the UI: go to View->Property Manager, add a new property sheet, then add other property sheets to that sheet (right-click the base sheet, Add new Project Property Sheet, just like for adding sheets to the project). You will see VS indents them to show they are imported into another sheet. The created property sheet will of course also use the Import element as in your answer.
I found the answer. I don't think there's a way to do it via the VS GUI, but if you open the .props file in a text editor, within the tag you can do:
<Import Project="other.props" />
and this will do what I was looking for.
However, if you edit the property sheet using the VS GUI, when the file is saved it will no longer contain the import reference
Related
I have an existing PowerPoint where several slides reference the same Excel spreadsheet that is embedded in the file.
I want to reference the same file in a new slide, but copying and pasting as object does not seem to work.
I tried going to the 'Insert' ribbon and selecting the 'Object' button. This did not allow me to reference an Excel object that already exists in the PowerPoint
You need to work through the Shapes.OLEFormat property, which allows you to run Activate and DoVerb:
ActivePresentation.Slides(1).Shapes(3).OLEFormat.Activate
I looked at an existing tutorial for registering the file type associations in iOS via XCode.
I added my a new entry under Imported UTIs for my self-defined custom file type like .teop and filled the field for Descriptions/Identifier/Conforms To/Icons. Unfortunately, there seems to be no button for Additional imported UTI properties, so I can't follow along the tutorial and I'm I don't know how to proceed.
I don't think you need that for a known file type like pdf. I just did a test and the additional properties were not necessary for a PDF.
I think they are necessary for custom file types though. If the properties are not available in the Advanced tab, you can set them in the Source tab. The advanced tab is just a GUI for the source tab for easy entry of document/imported uri types, etc. You could actually do it all in the source tab. Same is true for settings in the Application tab: just shortcuts to add key/values to the info.plist file. If you open the info.plist file in a text editor, you will see that it is just an XML file.
That said, in the source tab you can add the additional properties:
And there is part 2 of the guide you linked that discusses custom file types: https://www.infragistics.com/community/blogs/b/stevez/posts/ios-tips-and-tricks-associate-a-file-type-with-your-app-part-2
I'm trying to add Inherited Project Property Sheets to the configuration for a project.
I paste in the string
..\..\vs\library.vsprops;..\..\vs\debug.vsprops;..\..\vs\platformx64.vsprops
And click Apply/OK. As soon as I do the property is cleared (most visible when clicking Apply). What is going on?
As far as I can see, the way you normally create Property Sheets in Win32 (I am using the API, not MFC) programming is you have a bunch of dialog templates for each tab page, and you make the property sheet out of them. I have read about creating Dialog Templates 'in memory' but I would prefer not to do it this way. How do you add controls to a Property Sheet programatically at runtime, just like you can create a BUTTON and add it to a Window at runtime?
I suggest that you create a blank template and link that to your app. You can then create the property sheet with CreatePropertySheetPage and then add and remove controls to that property sheet as you please.
If you absolutely have to use a template built on the fly in memory, and you can't bring yourself to link a resource to your app, then you need the DLGTEMPLATE structure.
I need to create a from which uses the same ListBox as the one from Collection Editor of Visual Studio (The ListBox under the Members label). Please, explain exactly which WinForms control is this and which of its properties are set?
You can see the control I am asking about under the Members: label of every collection editor form in design time of Visual Studio.
Thank you.
Hopefully this can get you started. There's other (probably better...) samples out there, but this is a basic starter which can help you get the concept:
http://msdn.microsoft.com/en-us/library/9zky1t4k%28VS.90%29.aspx
Quote:
This example shows how to create a
control named ContactCollectionEditor
that implements a custom collection
editor. The example shows how to
specify the exact type of the object
that a page developer can add to the
control's collection property when
using a custom collection editor. You
associate a collection editor with a
collection property (or the type of
the property) by applying the
EditorAttribute to the collection
property of the control.