The full version is relatively inexpensive, and they do sell the sourcecode so compilation within a single EXE is a possibility.
I am no longer received the above exception. ASP.NET seems to find the proper assembly correctly. The trial version is fully functional, except for the restriction of only being able to read or write 120 rows.Īfter installing .dll version 12.0.0.0 into the GAC and restarting the server. It is a fully managed.NET component rather than a COM object and it allows you to read/write/manipulate Excel files whether the client has Office installed or not. Note that you'll have to enable logging by setting the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\EnableLog registry key to 1.If you are open to switching APIs, you can use a third party solution that is superior to the MS Office Interop in nearly every way. Microsoft has information about this tool here. If you still can't figure out where the old version is coming from, you can use the fuslogvw.exe application that ships with Visual Studio to get more information about the binding failures. (See my answer to this question for notes on creating a batch file to do this for you) This Microsoft article states that assemblies found in the GAC are not copied locally during a build, so you might need to remove the old version before doing a rebuild all. This will display the version number in the list of results, so you can see where the old version might be coming from.Īlso, like Lars said, check your GAC to see what version is listed there. Once you have a list of results, do View->Choose Details. First, use Windows file search to search your hard drive for your assembly (.dll).
You can do a couple of things to troubleshoot this issue.
0 kommentar(er)
