Thanks Pavel, My solution is located in a mounted folder, so that probably explains it.
On Fri, Jul 19, 2013 at 5:46 AM, Pavel Lyalyakin < pavel.lyalya...@visualsvn.com> wrote: > Hello, > > On Thu, Jul 18, 2013 at 11:11 PM, <ithiel...@gmail.com> wrote: > > > > I'm getting this error when I try to add a file or folder to my project. > I get the same error when I use the "Add to Subversion" context menu option. > > > > Why does VisualSVN think I'm adding a symbolic link? > > > > I'm using VS2012 on Windows 8. > > Thank you for the report. If access a working copy via a symlink or it > is located in a mount-point folder then VisualSVN 3.5.0 fails to > initialize when you open the solution in Visual Studio; you will get > "Symbolic links are not supported on this platform" errors. Do you > access the working copy by a symlink? > > We are currently working to fix issue. The issue is a critical one and > we consider to fix the bug in one of the upcoming VisualSVN versions > (3.5.1 or 3.5.2). > > As a workaround, you can access the affected solution / working copy > directly on filesystem, i.e. bypassing a symlink. > > -- > With best regards, > Pavel Lyalyakin > VisualSVN Team > -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/groups/opt_out.
