If I compare a local file to its parent file, I can edit, in the right pane of VS, the local file if the file extension is cpp or h. If I compare text files that have a different extension (e.g. file.abc), the comparison is against a copy of the local file (e.g. file - copy 2.abc), not against the local file itself, and the copy is not editable.
The file extension must be registered with the c++ editor (Tools | Options... | Text Editor | File Extension).
The following command line generates copies of the compared files.
devenv /diff c:\file.abc d:\file.abc compares c:\temp\file copy.abc to c:\temp\file copy 2.abc.
Is it possible to have the same behavior as for cpp & h?
Related
I have a backup files for Db and ibwant to open them vit unfortunately my license for sqlbase 7 server is not valid so is there is a way to open those files or convert them to any file type to use it . the files have .uld extension
.uld files are simply unloaded text files created using the UNLOAD utility in SQLTalk and should be just text files you can open with notepad. You don't need to convert them to anything.
If you can't open them with notepad - they're not true .uld and must have been renamed.
True backup files are .bkp, and are binary format - a totally different scenario.
I have the following issue-
On Team Explorer - Pending Changes there is an option that automatically detects added files to folders that are under source control. The problem is that more than 50,000 files are detected.
Is there any way to edit this list? to remove items I don't care about so it will be relevant when I do have files I want to add?
(I know I can add items in the Source Control but I want to make this option usable)
You can click the 'Detected' link to pop up the "Promote Candidate Changes" dialog, then select the files you want to check in to promote.
If you're using local workspaces, you can add a .tfignore file to ignore the files which you don't want to be detected in source control. eg: ignore by file extension .txt, then all the .txt files will be ignored in source control. They will not be detected.
Please see Customize which files are ignored by version control for details.
Please note that with TFVC you need to put .tfignore in every solution root.
.tfignore file rules The following rules apply to a .tfignore file:
# begins a comment line
The * and ? wildcards are supported.
A filespec is recursive unless prefixed by the \ character.
! negates a filespec (files that match the pattern are not ignored)
.tfignore file example
######################################
# Ignore .cpp files in the ProjA sub-folder and all its subfolders
ProjA\*.cpp
#
# Ignore .txt files in this folder
\*.txt
#
# Ignore .xml files in this folder and all its sub-folders
*.xml
#
# Ignore all files in the Temp sub-folder
\Temp
#
# Do not ignore .dll files in this folder nor in any of its sub-folders
!*.dll
I am trying to find a way to create a file that stores changes made to a folder and all files within it.
I have the path of the two folders I am comparing and the name of the output file. I need use these inputs to display files added or removed as well as lines added, removed or changed within the folder and store it in the file. The files in the folder are all text files.
Once this update has been changed I would also like to be able to use it to undo the changes made.
Example:
Folder 1
foo1.txt
This is some text in the file
foo2.txt
This file also has some text
This file has two lines of text
Folder 2
foo2.txt
There is some text missing in this file
Output file
foo1.txt added
foo2.txt line 1 changed
foo2.txt line 2 removed
In Xcode 7, you can create 'Run Script' phases in the Build Phases tab. At the bottom of the area, there's an 'Input Files' section and an 'Output Files' section.
I have a script that generates a .cpp file at $(DERIVED_FILE_DIR)/myfile.cpp. The file is listed in the 'Output Files' section of the phase. However, it appears that it's not compiled into my program, as the symbol that it defines are identified as missing by the linker.
How can I tell Xcode to compile this file as well?
One possible solution (which feels like a hack) is to insert the built file into the project, set its location (in the Identity and Type section of the Utilities bar) and then edit its location in the project file with a text editor for computer independence. In my case, the file entry (with newlines for readability) now looks like:
DC40C4121C7FC98F0087702A /* bindings.cpp */ = {
isa = PBXFileReference;
lastKnownFileType = sourcecode.cpp.cpp;
name = myfile.cpp;
path = "$(DERIVED_FILE_DIR)/myfile.cpp";
sourceTree = "<absolute>";
};
This is interpreted by the file browser as a file whose absolute path is literally $(DERIVED_FILE_DIR)/myfile.cpp (and the file always shows in red in the project explorer), but the build system will grab the file from the correct location.
I am running a third party sample MFC project:
In the "Output" tab of a successful build, this is shown:
1> MDIBars.vcxproj -> C:\Program Files (x86)\BCGSoft\BCGControlBarPro\Samples\MDIBars - Copy'\'.'\'..\Bin\MDIBarsD.exe
(I had to add two pairs of ' to get it to post correctly)
What does this mean? Specifically, the ".\" & "..\"
I know that .\ is the directory the .sln is in...
I know that ..\ means one up from where the directory the .sln is in...
The directory just before the .\ is the location of the .sln. So it appears there are identical consecutive directories in the file path? It looks recursive.
What am I missing?
The MDIBars Property Pages/Config Properties/Debugging/working directory is C:\Program Files (x86)\BCGSoft\BCGControlBarPro\Bin <\n new line>
The MSVS2013 solution file is here: C:\Program Files (x86)\BCGSoft\BCGControlBarPro\Samples\MDIBars - Copy<\n to make this post clear>
The solution file is called MDIBars.sln
ProjectDir: C:\Program Files (x86)\BCGSoft\BCGControlBarPro\Samples\MDIBars - Copy
Notice they do not have the MDIBars Property Pages/Config Properties/Debugging/working directory where the project .sln file is located.
Any help is appreciated...Thanks,
that is just an artefact of concatenating paths automatically.
. means "current directory", .., as you noted, means "one level up".
c:\xyz\.\abc is the same as c:\xyz\abc and c:\xyz\..\abc reduces to c:\abc (think of it as going to xyz, then one level up and to abc)