Here is my conundrum, I have a Visual Basic.NET project, I want the revision of the project to match that of the svn revision and to be updated dynamically but the only solutions I have found that 'work' without fault have to be installed on any computer that is going to work against the source code.
I.e. addition projects (such as using MSBuilds, svnRevisionlabeller, ...) or SubWCRev.exe (as in TortoiseSVN). All of which won't work if someone else uses a different svn client or I'd rather not have to import or use additional programs in my build process if I can use hooks in the repository itself to just update the AssemblyInfo file with the newest revision number.
Does anyone have any suggestions or am I just going to have to give in and use one of these solutions I listed earlier (leaning toward SubWCRev.exe)?
p.s. I am aware of the issues involved in modifying the content of a commit via hooks (and the working copy on the committing computer will not match, which is why I haven't attempted this yet).
According to this there is a Beta build that you could try if you wanted: https://kubuntu.org/news/plasm...eta1-available-for-testing/
But like they say, since it's in Beta you might want to wait for their next official release which I think is scheduled for October.
That’s not quite right. It’s not rdping into a Windows machine to use apps. This had existed in the past as RemoteApp where just the virtualized app(s) is/are presented to the user and not a full vm.
https://remoteapp.readthedocs.io/en/stable/remoteapp-anyapp/
Im guessing they just made the process easier now and are treating what they killed off as something new.
Question
Squirrelington
Here is my conundrum, I have a Visual Basic.NET project, I want the revision of the project to match that of the svn revision and to be updated dynamically but the only solutions I have found that 'work' without fault have to be installed on any computer that is going to work against the source code.
I.e. addition projects (such as using MSBuilds, svnRevisionlabeller, ...) or SubWCRev.exe (as in TortoiseSVN). All of which won't work if someone else uses a different svn client or I'd rather not have to import or use additional programs in my build process if I can use hooks in the repository itself to just update the AssemblyInfo file with the newest revision number.
Does anyone have any suggestions or am I just going to have to give in and use one of these solutions I listed earlier (leaning toward SubWCRev.exe)?
p.s. I am aware of the issues involved in modifying the content of a commit via hooks (and the working copy on the committing computer will not match, which is why I haven't attempted this yet).
Link to comment
https://www.neowin.net/forum/topic/948450-subversion-hooks-modifying-file-assemblyinfo/Share on other sites
3 answers to this question
Recommended Posts