Trent L. Taylor (05/26/2009)
[codesnippet]This is in no way what I was trying to suggest. That is why I was referring also to a "migration" as well. Migrations generally mean that there is a process to move forward. We have never been a company to stifle ourselves in this regard. We will move forward providing a clear path to move applications forward using new technologies that are available and coming down the pike.Thanks, glad to hear that. As for 3.5 I will do some test in the following weeks, since now I have to move forward with my current project, but if I can make my SF/.NET applications run from a shared folder it will make my life a bit easier since I am more comfortable with having one single application to update instead of multiple workstations, even though there are a lot of pro/cons to both type of installations and their maintenance and I may be searching for an "old dog" here
.
I am very concern on being able to lower the internal maintenance cost of my applications, and kind a like to build applications that will be maintenance free for the user in a sense of updating their current applications. For my VFP applications I had a very stable process using Stonefields tools and others and I am trying to get to that point with SF and DDT as well as other 3rd party tools.
On a second though, forget about everything we where talking here and bring us the SF Licensing Manager Tools instead
sorry, just thinking out loud
Edhy Rijo