If your application depends on the fact that Excel was installed for the correct and effective work, then inform the user about it. Catch the exception and pull out a notification to inform them of the problem, but then in this notification give them the opportunity to open it in an alternative editor such as notepad.
It all boils down to a good UX - let the user know, but do it in such a way that you provide them with opportunities, offering options to continue, and not just stop them and stop when such a small problem arises.
Edit: Do what you do, do not assume that they have Excel, they may have another editor / editor such as OpenOffice. No matter what is registered in csv, let it do it. Do not try to go and check the file association yourself, your application cannot (possibly, will not) have sufficient privileges to go in the background in the registry.
You also need to check for other obvious causes of exceptions, for example, the user does not have permission to open the target file, this may be due to restrictions set in the folder or the file itself. The file may have been locked because it is still open in another process. There are many reasons why your Process.Start may fail.
Catch the exception, and if the reason is not the application associated with the file, offer them an option. If the user decides to use Notepad, try opening the file in Notepad, but don't forget about the exceptions. Notepad is a good option, it does not contain a file lock, but it still depends on the ACL in the folder / file.
slugster
source share