|
So I have a program that was written in visual studio and goes through vb c# then to fortran to calculate values. I am trying to get this to run online and running into problems.
I first tried asp.net in vb where I created a new project and referenced the DLL's that were created by the original code, which only worked on the computer the original code was written on and would fail on my computer during the fortran transistion.
Stepping through the code did not solve anything either as when it cycled through the fortran code it would get to a certain part and fail. It gave me a chance to look at the disassembly because there was no actual error message and it had a file path in the problem area of the disassembly.
I have attached images of the problems I was getting during trying to solve this.
This error message appeared after running the asp.net program the first time before the browser popped up
http://i.imgur.com/kfUVKw7.jpg[^]
This error message appears after I have entered all the values in the input form and they get submitted to the code.
http://i.imgur.com/yaau5At.jpg[^]
I am wondering if it is an pathing error based from the second picture as the actual asp.net program was in my C:\users folder but the source file is saying C:\Data(which was the file structure for the computer the original code was written on) when it shouldn't need to go to C:\Data if all of the code is complied into dlls that are added as references.
I am now trying to implement it into python but am not getting as far, so if someone could help me out with the asp.net problem or have another way that this can be put online that would be greatly appreciated and I can also supply more information if it is needed.
|
|
|
|
|
Some comments on the ASP.NET error:
- Don't use
Catch ex As Exception; only catch the exceptions you're able to handle. - Don't use
Throw New Exception(...); always use a more specific exception type.
For example: Throw New InvalidOperationException(...). - If you're catching an exception and throwing a new exception, always pass the original exception to the
innerException parameter of the new exception. This will preserve the information about the original exception, which will make it much easier to debug.
Throw New InvalidOperationException(..., ex)
At the moment, all we know is that something within or called by your setPressureTemperature method has thrown an exception; we have no way of knowing what that exception was. - Once you've updated the code to pass the inner exception through, run your code again and look in the application event log. The full details of the exception should be logged there.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
