04/12/2009 4:58:40 PM
Anas
Posts: 4
|
Have anyone experience this error 'unknown namespace' when referencing an external dll into a T# project?
The class I need to test resides in an external DLL, I know there are known issues in T# intellisense in VS 2008. But I am sure I am using the correct namespaces in my test files, yet i keep getting the 'unknown namespace' error.
Any help is much appreciated.
I liked T# so much, I am trying to incorporate it into our unit test suites, but first I must resolve this issue.
Anas
"C#, B#, Stay#"
edited by Anas on 04/12/2009
<em>edited by Anas on 04/12/2009</em>
|
|
0
• permalink
|
04/12/2009 5:08:03 PM
Ludovic Dubois
Administrator
Posts: 155
|
Do you have the latest version (1.7.1?)
Do you have the same problem as this one: TSHARP-125?
Is it an DLL from another projet in the same solution?
If you can reproduce it in a small example it will be appreciated. We need to know more information.
What you can do is adding an environment variable TSHARPLOG to point to any folder, a log file will be created for any error encountered in a VS session.
Thus, enter Visual Studio, recompile and see the log file for any error inside.
Thanks.
|
|
0
• permalink
|
07/12/2009 12:20:42 PM
Anas
Posts: 4
|
Ludovic Dubois wrote:
Do you have the latest version (1.7.1?) Yes. I have version 1.7.1.922 installed
Ludovic Dubois wrote:
Do you have the same problem as this one: TSHARP-125?
Ludovic Dubois wrote:
Is it an DLL from another projet in the same solution? It is a DLL from another solution.
Ludovic Dubois wrote:
If you can reproduce it in a small example it will be appreciated. We need to know more information. I will do my best to reproduce it without using our production code which I can not send in an example for proprietary reasons.
Ludovic Dubois wrote:
What you can do is adding an environment variable TSHARPLOG to point to any folder, a log file will be created for any error encountered in a VS session.
Thus, enter Visual Studio, recompile and see the log file for any error inside.
I have added this variable both as a system and a user environment variable, but did not see any logs created.
Much appreciation for your always prompt replies. I will do my best to reproduce the error in an example.
"C#, B#, Stay#"
Anas
|
|
0
• permalink
|
05/11/2010 9:57:45 PM
robdud
Posts: 2
|
I have got the same error message. It is connected to classes with doted namespace. So if for example class which I want to test is "My.Super.Long.Namespace.CarClass" then problem appears. But if my class is MyOneWordNamespace.CarClass then there is no problem. Obviously it is unpractical as it is now.
Also when I write:
UIThreadDispatcher o = new mock UIThreadDispatcher(null);
only words "new" and "null" are written in a different color than default (black), which indicates that they are not treated specially by VS.
I use VS2010 Version 10.0.30319.1 RTMRel.
My version of Visual T# is 1.1.7 (though windows uninstaller says: "Pretty Objects Visual T# v1.9.4 (build 1200)")
<em>edited by robdud on 06/11/2010</em>
|
|
0
• permalink
|
06/11/2010 9:47:14 AM
Ludovic Dubois
Administrator
Posts: 155
|
robdud wrote:
I have got the same error message. It is connected to classes with doted namespace. So if for example class which I want to test is "My.Super.Long.Namespace.CarClass" then problem appears. But if my class is MyOneWordNamespace.CarClass then there is no problem. Obviously it is unpractical as it is now.
OK, I will see that this week and fix it.
rordbud wrote:
Also when I write:
UIThreadDispatcher o = new mock UIThreadDispatcher(null);
only words "new" and "null" are written in a different color than default (black), which indicates that they are not treated specially by VS.
Exact. mocks will be available in v2.0 of Visual T#, we are still v1.X!  It takes me lots of time to port both versions (v1.X and the other private branch for V2.0) of T# to VS2010 and .NET4 whose security has changed.
I can contact you when T# v2.0 alpha will be available to some people if you want.
rordbud wrote:
I use VS2010 Version 10.0.30319.1 RTMRel.
My version of Visual T# is 1.1.7 (though windows uninstaller says: "Pretty Objects Visual T# v1.9.4 (build 1200)")
edited by robdud on 06/11/2010
v1.1.7? Where did you find this number? It should automatically change at compile time by our integration server!
|
|
0
• permalink
|
07/11/2010 12:57:45 PM
robdud
Posts: 2
|
I don't remember where did I take that number from (1.1.7). Possibly I imagine it, sorry (just couldn't find it again today).
Please let me know when T# v2.0 alpha is available. I really like to use mocks (they work quite like moles but with less code).
Also if you could, let me know when you fix that namespace problem, as it doesn't let me work with T# at all. (and I have read the whole manual just to realize after that that nothing works 
|
|
0
• permalink
|
15/11/2010 1:16:02 PM
Ludovic Dubois
Administrator
Posts: 155
|
Hi.
Last wee, I sent you a private message with a small project trying to reproduce the problem you encounter. Did you receive it? Did you register with a valid email address?
I was unable to reproduce the problem with the exact name you provided!
Please, help us to help you!
|
|
0
• permalink
|