When publishing several WPF apps, writing the same name on 'Suite name' seems to override the previous app in the Start Menu folder.
The Publisher name more or less defines the Start Menu subfolder name and Product name defines the application name. And if I just leave the Suite name blank all the apps are in the Start Menu subfolder together. From what I could find about it, it should define a group of things that will be used together.
So my question is: What does Suite name even define?
Related
I'm trying to connect my database to Altium using *.dblib file. After i connected, i have chosen neccesary table and mapped design parameters to database field names:
Then i have tried to use components from this table in my project, but "Place" button was disabled, and there was no any previews, but paths in "footprint path" and "library path" are valid:
Also if i try to open symbols or footprints using popup menu in table, nothing happend, but as i already said, paths are valid:
What i'm doing wrong?
Usually I experience this when I forgot to add paths in the model and search path.
By pressing the Option button in the DbLib file.
I have not added footprint paths or library paths as separate entries in the database though.
But you say this is properly entered, and I can only think of one other issue:
I have experienced that if I change the database, mdb files I need to restart Altium before I see the components appearing in the preview.
I am using Visual Studio 2017 to write some stuff in C. When I open a new project, I have some default filters and in "add" option for the project there's only filter and no folder/directory.
I want my project to have a folder structure, but can't add folders to the project in Visual Studio. Looking online I can only find solutions for adding an existing folder to a project and not adding a new one.
How can I add new folders to a Visual Studio C project?
How can I disable filters?
The way that I think of Visual Studio 2017 (earlier versions of the IDE as well) and its presentation of files in File View is as a kind of virtual file organizing system. File View allows you to logically organize files, presenting the actual file system in a more helpful manner.
The icons that look like folders in the File View are not really folders but are instead labels, called filters, which allow you to group your files however you like regardless of how they are physically stored in your persistent storage area such as a hard drive.
Filters are more flexible by not corresponding to the physical file folder hierarchy as they allow you to organize files that are all in a single folder into logical groups. Filters allow this to be done at a finer grain than is typically used by grouping files in folders. Filters also allow you to group files that are in multiple folders together into a single logical folder within File View.
However filters can be confusing because most of us are so accustomed to file folder hierarchies that the filter methodology can disconnect the logical file as represented in a Filter from the physical file location located in a folder.
My typical methods of adding files
Typically what I do is to create the physical folders through Windows or doing a clone of an existing Git or Subversion or VS Team Services source tree. With something new I may use the New Solution or New Project wizard to create my initial starting point and then organize and add files and folders physically through Windows and then go into the Visual Studio IDE to create the Filters and then Add existing files to the Filters. In some cases I will create sub-filters within a Filter in order to better organize the files within a physical Folder.
For new files I will just use the Add New Item menu option to add the item to the proper project. If you right click on a filter name, the new file will automatically be added to the filter. In some cases when I have added additional filters to the project to organize files, I will drag the newly created item to the proper filter and drop it there.
This drag and drop is not changing the physical location of the file but is changing its logical position by moving it from one filter to another. To move the file physically from one folder to another, I will usually do that with Windows. Just remember that if you do physically move a file with Windows you must also modify the file's entry in the Visual Studio 2017 filter to which it has been assigned, I usually do a Remove on the file followed by Add Existing Item and browse to its new location.
It appears you can not have the same file in multiple filters within the same project.
In some cases when I Add New item, I will change from the suggested folder displayed in the Add New Item dialog to a different folder using the Browse button. And if I need a different extension to the file then I will make that change as well, a common action when adding a new C source file to a project which requires changing the .cpp extension to .c.
You can also use the Browse button to navigate to a folder where you can then create a new folder if you like using the right click menu that displays when you do a right click in the displayed list of files and folders.
Unfortunately, the Add New Item dialog always wants to put a file into the project directory with all the other files. The Add Class wizard doesn't give you the opportunity to specify anything other than the default project folder. I have in some cases created C++ classes using the Visual Studio IDE, removed them from the project, moved the physical files to where I want them to be and then added them back to the project.
The filter approach seems to work well because the total solution is divided up into multiple projects and each project has its own physical folder. The multiple projects may correspond to particular DLLs or static libraries or other components that are used by the solution.
See also Can I configure Visual Studio to use real folders instead of filters in C++ projects?
Example screenshots of folder and filters
Here is a Windows folder view of a small project of the resources being used:
And this is how I have the filters set up. Normally the list of resource files can be quite long however I have created two sub-filters to logically separate out bitmap files from icon files though they both share the same physical resource folder.
Also the filter named PepIncludes corresponds with an actual physical folder named the same while the filters named "Header Files" and "Source Files" are groups of files that all reside in the same physical folder which is named the same as the project folder.
The following screen shot shows how filters can provide flexibility. I have a folder with include files, PepIncludes, and I have the same collection of files in two different projects within this Visual Studio 2017 solution. In a solution with 30 or 40 projects, this can make it a lot easier to manage files. For instance you can see that after modifying the file "ECR.h" the fact that it has been modified shows in both of the filter file listings (the small red check mark next to the name).
I know that I can use 'Ctrl + p' to find file and open it. But it search file in all projects. What is the way to search file only in current project?
The Ctrl+P key binding opens what is known as "GoTo Anything". The Sublime Text Unofficial Documentation on GoTo Anything states (emphasis added):
As you type into Goto Anything’s input area, names of files in the current project will be searched, and a preview of the best match will be shown.
Further down in the documentation in the "Sidebar" section it states:
The sidebar provides an overview of the active project (more on projects later). Files and folders in the sidebar will be available in Goto Anything and project-wide actions like, for example, project-wide searches.
Projects and the sidebar are closely related. It’s important to note that there’s always an active project, whether it’s explicit or implicit.
I would bet that your current active Sublime project includes files which should be moved to a separate (explicit) project and that is why they are being included in the search results contrary to your desire. To learn more about projects, read even further down in the documentation in the section titled "Projects".
Maybe you can try this one: Shift+Command+F, then you can enter search keyword as follows:
Find: Please enter search keyword
Where: Select the project location
I am using Xcode to learn C. I made a project named Learn C, and I would like this to contain many exercises, like ex11.c, ex12.c, etc. However, this does not work, because all my exercises need the main function, but only main.c can have it.
In Eclipse, I would be able to make a workspace named Learn C, and have many .java files in it, like ex11.java, ex12.java, etc, to keep myself organized.
Does anyone know how I can recreate this in Xcode?
Thanks!
You can do this in Xcode as well. For each exercise, you need to create a new target. To do that, open your Xcode project, click on the Project Navigator tab, and select the project. Then, from the "Editor" menu, select "Add Target". If you're working with examples from a book or web page that isn't Mac-specific (or iOS-specific), you'll want to select "Command Line Tool" as the type of target. Xcode will create the new target and you can add your new ex*.c file to it.
Start by creating a workspace:
Open Xcode.
Pull down the File menu and select New Workspace...
You will be prompted for the name of the workspace and optionally a target folder to create it in. Select New Folder in the lower right corner and create a folder called Learn C. Then, select Save. A new workspace will be created in your new folder.
Once you have that you can create new projects within the new workspace. To do this...
Right-clck anywhere in the workspace explorer on the left-side pane of Xcode and select New Project....
Select OS X Application from the left pane, then (if this is just C code) Command Line Tool from the right pane. Then select Next.
Enter the name of your product (in your case, Ex1 would be your likely first product). Select the appropriate language, in your case C.
On the next wizard pane, when prompted for the location of the new product, the default settings should be sufficient, but in case they're not set correctly, make sure both Add To: and Group: have the Learn C workspace selected. Press Create.
To select which project you're building at any given time, select the active "scheme" by navigating the Product/Scheme menu and clicking on the project you want to build, or select the scheme using the button bar (its the bottom immediately to the right of the "Stop" button in the upper-left of the bar).
This should create a new project in the Learn C workspace. You can repeat the project-creation steps above (not the workspace creation; you already have one of those) for as many projects as you want, so long as their names are unique. Once you get the hang of this, you will be able to share code between projects using the advanced capabilities of the workspace and project management features, but for now this should be enough to get you going.
More information can be found on the Apple Xcode Developer Website (assuming you've shelled out your $99 annual developer fee). There is a wealth of info on Xcode, and though it (imho) isn't as snazzy as the likes of Visual Studio on Windows, it becomes natural after some time (like all things). The section titled Maintain Your Code and Other Resources in Projects or Workspaces will probably lead you further down the path you're interested in pursuing.
Best of luck.
It is possible to export settings from one project and import them in another.
However, it seems that only "include Paths" and "Symbols" can be moved to a new project this way.
Is there any reliable way to copy all settings? Particularly I would like to copy the linker settings for my embedded ARM project.
I do not want copy the settings manually, as this is something that will have to be done often by at bunch of people.
The easiest way I've discovered to duplicate the settings for a project is to use another workspace. It takes a few steps to set up but you should only need to do it once.
1. Start a 2nd copy of eclipse and select or create a new workspace.
2. Import your baseline code.
3. Rename the project to something generic like NewProject
4. If your project has files you don't want to be imported into new projects delete them. I find it helpful to keep a few (like main.cpp)
Now back to your original workspace.
1. File->Import->Existing Projects into Workspace Next button
2. Use Browse... to go to your newly created workspace and select NewProject.
3. Check the Copy projects into workspace checkbox.
4. If you have warnings about the project already existing try clicking the Refresh button and make sure you don't have a folder in the current workspace with the same name. [ You can delete a project but not remove it from the hard disk so you have to make sure the intended folder name is not in use. ]
5. Rename the project to your desired name.
6. Start coding...
All the toolchain settings, include paths and library paths should be intact. It seems like a lot of work, but once you do it once its not too bad (as long as you can keep duplicating that one project).
This can be done in simple steps. Useful if you do not want to create new workspaces.
Open the project in the workspace.
Click on project and copy.
On the project tab area, paste the project.
Eclipse asks for a name, rename it to a new project.
Click Ok.