Difference between different project files in Netbeans - file

I have in my working environment always more then one project open, some of the have same files but are from different project, and finding out which of them are from which project can be a real pain in the ass(however 2 sec over the div and see which folder are they from)
Is there a way to mark them so i can tell which file is from which project?
I am using NB 7.3 64bit for Windows.

There is a plugin which shows the path in the title: http://plugins.netbeans.org/plugin/42000/show-path-in-title
And if you are switching files via CTRL+Tab the path of the selected file is shown on the bottom of the window.
Maybe this helps.

The window title for me is: "{project name} - NetBeans IDE 7.2.1". Directly on the tab I don't know how to put this information, but I use "View -> show versioning labels". Instead of various projects open, I have various "instances" of the same project on different branches in my VCS.
I'm using Ubuntu.
UPDATE
Just reinstalled NetBeans 7.3 on a Windows VM and the behavior is the same: project name prepends "NetBeans IDE {version}" in window Title.

Related

Guibuilder right menu option not available

Using Eclipse Photon and the newest version of the Codename One plugin, I have an issue where I create a new project and then create a GuiBuilder form inside that project, but when right clicking on that form I do not see any of the Codename One specific options I should be seeing, like the Guibuilder option. So I can't open the form in the Guibuilder.
This is happening in a 36 seat computer lab, but not on my office machine. Any ideas what might be going wrong in the lab?
If anyone else has this same issue, as Shai suggested, it had to do with where the Eclipse workspace was located. In my case I had it on the lab desktop.
There were spaces in the path, but even removing those did not solve the problem if the workspace was on the desktop. When I moved the workspace to the user folder, all started working as I would expect it to work.
There might be an issue with the length of the workspace path, along with special characters. Regardless, relocating the workspace to c:\users\win10\workspace solved the issue for the lab computers.

The CN1 Intellij Plugin is suddenly disabled on old project. Is it safe to delete an old ~/cn1Settngs/CN1Properties to fix this?

Strange issue I'm having and I want to know what to do to fix it without compromising project integrity.
I have a CN1 project in Intellij (v 2017.1.4) that I started a long time ago. The other day I started a new CN1 project to try out something new. It pulled down the latest CN1 libs (the properties file says version 174 is the libVersion) and worked fine for testing.
Now I open my original project and the CodenameOne functions are all greyed out (projectLibs version in the properties file is 159). The icon on the context menu and menu-bar are greyed out. The plugin is up to date (3.7.2). I see no messages or errors in the IntelliJ "messages" section.
I am assuming that the new project and libs re-wrote something common to both projects and now the old project can't even start the plugin to let it pull down new libs... In experimenting, I went to my home directory ~/.cn1Settings and renamed the "CN1Preferences" file so that the project would have to create a new one. When I opened the project it DID create a new one and the plugin was working.
So here's the big question: If I abandon my old CN1Preferences file, what settings/customizations in that file am I walking away from and will I need to make sure I set correctly again to ensure my project works as it should and doesn't have any hard to debug issues?
This is probably an issue of keeping two windows concurrently, try closing both projects and opening only one at a time. There is an issue with detecting the correct project in the IntelliJ/IDEA plugin

Xaml files inside a shared project appearing differently in VS2017

I have a solution, containing a shared project:
This contains a number of Xaml files:
However, when I open the exact same solution in VS2017, I get this:
The problem seems to cause any XAML files to be invisible within the project. The solution compiles and runs fine - is there something that needs to be installed or switched for VS2017 to treat shared projects correctly?
First Solution
(1) Exclude
(2) Show All Files
(3) Include all the files
Found some similar post may be work for you (seems to be some sdk needs to be installed)
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/26291339-e8fd-4596-980a-7befa63a1f7c/missing-folders-files-add-item-options-in-shared-project?forum=visualstudiogeneral
Thanks
Using the Visual Studio 2017 Installer, add support for Universal Windows Platform Development. That will connect each xaml to its respective xaml.cs in a shared project.
One would think that .Net Desktop Development would be enough to do the link, but it is not.

Eclipse EE can't expand folder called 'services'

I am developing a mobile application using IBM Mobile First using AngularJS in Eclipse EE. I have a basic file structure containing folders 'controllers', 'directives', 'filters' and 'services'. The problem is with Eclipse: In the Project explorer I can't seem to expand the 'services' folder. I can see the content of the folder in Windows Explorer as well as Sublime Text File three. When I rename the folder to something else I can however expand it in Eclipse.
What is the cause? Is there a solution to this problem or is it just something I have to live with? Any suggestions on alternative names then? I have to use Eclipse due to policies at my workplace.
There is special treatment by some Eclipse versions for folders named "services". By default, at least in some views such folders are hidden.
You can modify the view settings to turn off this very annoying behaviour. Bring up the view menu by clicking the little triangular icon, top right
select Customize view and in the content tab unselect Services Navigator Content.
Your services folder will now be visible.
I believe there was once such an issue in MobileFirst - so I suggest one of two things:
Download the latest Studio update from IBM Fix Central, or the one from the Eclipse Marketplace.
Use a different folder name.
Had the same issue.
There is a folder named 'services' created by MobileFirst by default(It is present after the 'server' folder).
So rename your 'services' folder to just 'service'. This is what I did.

clickonce file missing

Using Clickonce with VS 2010 and .NET framework Client profile 3.5, I have several file folders with application level XML and/or textfiles that are needed at runtime.
The file folders sits in the same project where they are to be used.
These files are marked as "Copy always" at compile.
Build Action is "Content".
On my development machine the files are actually copied into the ./Bin/Release/myFileFolder/xxxxx and all is fine.
On user's computer, install runs fine but some files are reported missing at runtime when the program need them.
Do I miss something? Is any file specific option deep hidden in the option list?
Help please! and .NET framework 3.5
If the files are in referenced projects then they are not included in the click once publish by Visual Studio. You can verify this by checking the application files dialog in the publish page of the project properties.
Assuming this is the case to get these files included you can either add them as links in the main project itself or edit the project file to include extra files in the manifest. See ClickOnce Content Files for information on how to do this.
I can confirm that this can still be an issue in Visual Studio 2019.
I have been working on DevExpress dashboards that consume XML files at runtime to produce their dashboard layouts, and whenever I would publish my project, I would get a bizarre error about the XML file not being found when clearly it was published to the same output directory as the rest of the project.
Just to be clear, the XML file existed in my Visual Studio project and was set to Build Action = Content and Copy Always To Output Directory.
What I had to do was what was suggested in this answer:
Go to Project Settings.
Open the Application Files list.
Change the Publish Status of the XML file - which Visual Studio automatically set to Data File (Auto) - to Include.
Voila. FileNotFound error magically disappeared after publishing the project.
A workaround is to make your application create the xml/txt files if they dont exist.

Resources