I apologize for the simple questions posted here but I am fairly new to Flare and completely new to TFS. My company is in process of upgrading TFS to 2013 version. I have not linked the Flare projects to TFS yet so don't have concern with the upgrade per se but have been asked to answer some questions regarding the upgrade and my future needs that I am not able to answer with my current knowledge of TFS. I hope others can assist.
Flare needs to run projects off local workstations and will use TFS as the source control only to maintain archived versions of the files/development/production files for the projects. The published locations are on company SharePoint sites. I have been asked to respond to TFS upgrade questions by my company and want to make sure I have the knowledge needed to answer them.
1. Do you use build servers associated with TFS to build your code? as I understand it No-Flare is my code source.
2. Are you using build servers for your PROD environment? again No-SharePoint is published location and Flare produces the production files in the location workstation-correct?
3. Which version of Visual Studio do you use? 2010 ? 2013? Or 2015? Do I have need of Visual Studio with the way that we intend to integrat Flare with TFS?
Thank you for all your assistance in confirming my assumptions on these things.
Flare 12 and TFS Help
Re: Flare 12 and TFS Help
shloter, my response is numbered to coincide with your questions.
1 - No build server per se is required, however, technically speaking Flare is not your source code either. Flare is merely the software used to generate or compile your project files. The source of your content I imagine would be the htm and other files within the project. The entire output requires all of the supporting javascript and other files in the output folder of your target.
2 - In my case I post output to a web server. You can publish your output files wherever you like. I do not believe you can (or would even want to) configure Flare to directly produce the output on the sharepoint server. Instead, you would produce your output on a local computer (your workstation where Flare was installed) and then use a destination file to send your files to sharepoint.
3 - I use Visual Studio 2013. You certainly would need some version of visual studio. The reason is that Flare and TFS have never been a completely harmonious marriage. In all likelihood somewhere along the line you will need to perform an operation in VS that cannot be entirely achieved in Flare. Deleting files is one aspect where this is the case, at least for me. Even if there are seemingly no problems you can detect, it's sometimes a good idea to check VS even if just to ensure it (VS) believes you have the latest files.
1 - No build server per se is required, however, technically speaking Flare is not your source code either. Flare is merely the software used to generate or compile your project files. The source of your content I imagine would be the htm and other files within the project. The entire output requires all of the supporting javascript and other files in the output folder of your target.
2 - In my case I post output to a web server. You can publish your output files wherever you like. I do not believe you can (or would even want to) configure Flare to directly produce the output on the sharepoint server. Instead, you would produce your output on a local computer (your workstation where Flare was installed) and then use a destination file to send your files to sharepoint.
3 - I use Visual Studio 2013. You certainly would need some version of visual studio. The reason is that Flare and TFS have never been a completely harmonious marriage. In all likelihood somewhere along the line you will need to perform an operation in VS that cannot be entirely achieved in Flare. Deleting files is one aspect where this is the case, at least for me. Even if there are seemingly no problems you can detect, it's sometimes a good idea to check VS even if just to ensure it (VS) believes you have the latest files.