I wrote a Python script that edits emails and appends them to a folder with the IMAP "APPEND" command. The emails are successfully "created" as I am able to fetch them from the destination folder after the execution of the APPEND command. The problem is that the newly created e-mails simply won't show up in Outlook. It is worth noting that the destination folder contains older e-mails (previously created with my script) which are still visible in Outlook. I removed all Outlook filters from the concerned folder but still there are no new emails showing up. I also pushed the "Update folder" button but still no success. There is probably some advanced Outlook configuration that I am missing here ;) I would appreciate some help.
I "solved" the problem by simply removing and re-adding the concerned account ("Account Properties" -> "Account Settings" --> "Remove"/"Add"). Now I will have to wait and check if the problem reappears.
If this does not solve the problem maybe try with another profile.
Related
The above error recently started being thrown when I was making updates to an existing C# windows app that saves a folder location for files it uses.
Upon receiving this error, I found that my whole hard drive seems to be set to read only. (recently had to build a new dev system) I have tried changing the folders back to being readable via folder properties. Dialog pops up and goes through all the files as if it were changing the properties. When I open the properties immediately after, the folder is back to read only.
I have also noticed that VS IDE does't save changes to the recent files/projects.
Anyone experience this and have the solution?
Things I have tried:
created a new admin user. Logged in and found the same situation. Not tied to my profile.
Tried command prompt changing folder attributes with attrib command.
Tried changing my users permissions to full control.
uninstalled OneDrive (to eliminate possible syncing issues)
Turns out my AppData folder hidden property was set to true. Setting this folder and all sub folders to not be hidden fixes everything.
Is there any recommendable solution to integrate SVN with TFS 2013 in a sense that SVN is being used for source control and TFS for work item tracking?
For example, it should be possible to link commits in SVN to work items in TFS.
You can use Integration with Bug Tracking Systems / Issue Trackers: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html
It is very common in Software Development for changes to be related to
a specific bug or issue ID. Users of bug tracking systems (issue
trackers) would like to associate the changes they make in Subversion
with a specific ID in their issue tracker. Most issue trackers
therefore provide a pre-commit hook script which parses the log
message to find the bug ID with which the commit is associated. This
is somewhat error prone since it relies on the user to write the log
message properly so that the pre-commit hook script can parse it
correctly.
TortoiseSVN can help the user in two ways:
When the user enters a log message, a well defined line including the
issue number associated with the commit can be added automatically.
This reduces the risk that the user enters the issue number in a way
the bug tracking tools can't parse correctly.
Or TortoiseSVN can highlight the part of the entered log message which
is recognized by the issue tracker. That way the user knows that the
log message can be parsed correctly.
When the user browses the log messages, TortoiseSVN creates a link out
of each bug ID in the log message which fires up the browser to the
issue mentioned.
Go through mentioned URL for detailed description.
https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html describes how to configure folders in TortoiseSVN to do a one-way integration between file versions committed in TortoiseSVN, and work items in TFS. When a developer commits the file version, he/she is prompted for the TFS work item number (which works fine if the developer knows the number). It even creates a link to the TFS work item in the Revision Log of the file in TortoiseSVN. However, it does not display a list of work items for the developer to choose from, nor is there any link in the TFS work item going back to the committed file version in TortoiseSVN. (It is possible to write an issue tracker plug-in for TFS to do this, but all the plug-ins I have found on the internet seem to be for older versions of TFS.)
This integration will insert the bug number into the Revision Log of committed source files, and will add a link from the log to the selected bug in TFS. Although you make this change inside your working copy, it will apply to the same folder in other working copies once those working copies have been updated.
To associate a folder tree in TortoiseSVN to TFS:
1. Right-click on the folder in your working copy. This should be at the apex of the folder tree you want to associate with a project in TFS. Select TortoiseSVN > Properties.
2. On the Properties - TortoiseSVN window, check to see whether there are any bugtraq properties for this folder. If not, click New > Bugtraq (issue tracking integration).
3. The Edit Bugtraq Properties - TortoiseSVN window opens.
a. For Issue tracker URL, specify the URL to your work items:
http://tfs_server_name:8080/tfs/DefaultCollection/TFS_Project_Name/_workitems?id=%BUGID%&_a=edit
b. Next, place a check in the "Remind me to enter a bug-ID" checkbox.
c. For Message Pattern, specify something like:
TFS Work Item: %BUGID%
d. For Message Label, specify something like:
TFS Work Item:
e. For "Bug-id is", specify Numeric.
f. At the bottom of the window, place a check next to "Apply property recursively". Click OK.
4. Back on the Properties - TortoiseSVN window, verify that the bugtraq properties have been added and click OK.
5. Remember to perform an SVN Update and SVN Commit on the folder after changing its bugtraq properties.
The bugtraq properties that implement this one-way integration between SVN and TFS are built into Apache Subversion and so should work for SVN even if you are not using the TortoiseSVN user interface.
I am still using Microsoft Visual SourceSafe.
How can I add a journal to my projects?
By journal I mean a file, where all the changes in my projects will be logged to.
For example, when I check in a file named 'space_report.sql' in the journal it will be said
space_report.sql was checked in by "user name" at "the time when it happened".
I used to have this set up, can't remember how I did it.
right click the folder or file. and select view history.
if you view history of a folder, then you have the option to recurse to sub folder.
try it and let me know
I am using VS2012 with TFS on a server workspace.
When someone checks something out a person icon is shown next to the file so you know it is currently locked by someone else, however when they check it back in the icon changes back to a lock icon without any indication that the files has been updated.
Is there a setting i'm missing that will show that you don't have the latest file maybe an icon next to the file in the solution explorer?
The only way i see how to do it is to view history on each file or go to the source control explorer and run a compare on every files, both of these options are not very efficient as I would not know when to perform this so i would have to do it on every check out.
Thanks in advance.
No, you did not miss any particular detail. After the checkin, the icon returns to a lock, and there are no notifications by default.
I believe that there is nothing that can be done about the padlock icon, but you can set up alerts (e-mail) to be triggered when check-ins are made.
Take a look here and here (alerts for specific folders) to understand how to configure e-mail alerts using TFS Event Service.
You can also bind notifications to workitems.
If your TFS is configured to use gated-checking to perform a build on a "build server" before each check-in, you can subscribe to the Team Foundation Build Notification to receive notifications of new builds that were queued/processed on the server.
Hope it helps.
We have a 2008 solution that has a file system website as part of the solution. This solution is under source control with Team Foundation Server. Every time the solution is closed it either checks out a file called vwd.webinfo or attempts to and complains that someone else already has it checked out.
Removing the file from source control does not fix the issue because it gets re-added automatically for some reason.
Why does this happen and is there something we can do about it to remove this nag?
Thanks a lot!
open "source control explorer"
find vwd.webinfo in the correct path
click "delete"
chek-in the operation to solve this problem
The file will still be in your file system and solution, but not under source-control. You won't see "plus" or "v" or "lock" button
Go to Property Pages, select Build on the left, and uncheck "Build Web site as part of solution" Then you can delete the file and it won't get created automatically.
You should be able to delete this file manually and have it not reappear. This file holds some information that used to be located elsewhere in the project in earlier versions but apparently is not necessary. Close your solution before deleting the file from source control and on the disk.