Flex Builder 3 Beta 2 - Virtual Path Issue Vault & Fortr

robertjcollins · Post by **robertjcollins** » Tue Oct 30, 2007 5:21 pm

OK, I was able to load both plug-ins and they work great except if you have a Flex 3 ASP.Net Project (new feature in Flex 3). When you create a new project in Flex and specify that it will be used in a ASP.Net project it will create the VS.Net project, V-Dir, and configure IIS (pretty sweet). However it still holds the Flex Source in My Documents / bla bla bla and then Flex Builder creates a "Linked Path" to the bin so when you build in Flex it outputs you flash into the ASP.Net bin. However Fortress throws an error and states that it does not support Linked Paths:

[error]

Could not create repository folder $/OpenFlexCommerce due to Project 'OpenFlexCommerce' contains linked URIs but the'com.sourcegear.fortress.team.RepositoryProvider' repository provider does not supported them.

[/error]

Any thoughts?

Best Regards,

Robert J Collins

shannon · Post by **shannon** » Wed Oct 31, 2007 10:34 am

We don't support linked items, unfortunately. If you change the output folder to a folder within the project directory, you should be able to version control the project (this can be changed from the project properties, under Flex Build Path).

robertjcollins · Post by **robertjcollins** » Wed Oct 31, 2007 11:20 am

Yes, that is what I did. I just wanted to make sure you were aware of the issue.

Thanks,

Rob C