Hi,
Please keep the conversation on the list, so that if someone else knows the solution they can jump in.
I have no idea what exactly is happening in your case. TortoiseSVN is a client for Subversion. If you use it to commit, from right clicking in Windows File explorer, it will commit selected changes to the Subversion server. Shouldn't matter if Visual Studio is there or if the files are instead used with some entirely different program.
Did you commit to a different branch?
Had you perhaps not selected the changes in the file list in the commit dialog? (If no, the changes should still be in your local folder unless you actively used the "revert" function in TortoiseSvn.)
You say "visual studio" and "solution integrated in SVN" - I'm not entirely sure what you mean, but Tortoise SVN is only available in the Windows File Explorer. If you mean that you are accessing Subversion commands from within the Visual Studio IDE, this means that you have installed some other Subversion client that does integrate with Visual Studio. On the other hand, if all you mean is that you have committed the Visual Studio project files and code to Subversion using TortoiseSvn then that's fine. Neither TortoiseSvn nor Subversion itself cares whether or not the files came from Visual Studio. It can handle just about any file.
/Oskar