Bug 11027 – Visual D and perforce do not go along

Status
RESOLVED
Resolution
WORKSFORME
Severity
normal
Priority
P2
Component
visuald
Product
D
Version
D2
Platform
All
OS
All
Creation time
2013-09-13T13:20:41Z
Last change time
2019-05-11T14:48:39Z
Assigned to
No Owner
Creator
Rainer Schuetze

Comments

Comment #0 by r.sagitario — 2013-09-13T13:20:41Z
original report: http://www.dsource.org/projects/visuald/ticket/110 reported 02/02/12 08:40:54 by Anonymous for version 0.3.30 bug in Language Service for reasons i cant change here at work we use perforce and as i recently found out, visualD and perforce wont go along very well. if i bind my visuald project to perforce it sais something about something not being implemented and it wont check out (make writable) my d files once i start editing them as it should do. free perforce trial can be grabbed. would be awesome if u could make that work. Comment 1: 03/16/12 08:07:04 by Anonymous I also have a big +1 on this! I need perforce integration to work at work. Comment 2: 03/17/12 04:36:46 by sagitario I investigated this a bit recently, but haven't got a clue of what is going wrong. I'm not familiar with perforce at all, but it seems it uses a rather different approach to VS integration than other source code management systems.
Comment #1 by r.sagitario — 2014-02-26T23:26:57Z
I have added support for git-extensions in V2013, maybe this also helps perforce. If anyone can try it out, please report back.