Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
NCrunch 1.36b and VB Imports Statement
Options
Previous Topic Next Topic
MetaSam
#1 Posted : Monday, December 19, 2011 10:01:10 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/7/2011(UTC)
Posts: 7

Was thanked: 1 time(s) in 1 post(s)
Hi,

I downloaded the new version of NCrunch and I have the following problem (which I didn't have previously). I have a VB Imports statement with this form:

Code:
Imports ShortName = Some.Long.Path.To.Namespace


NCrunch 1.36b doesn't seem to like it. I have the following error:

Quote:
'ShortName' is not declared. It might be unaccessible due to its protection level.


I'm using Visual Studio 2010 / .NET 4.0. Thanks.

Sam
Back to top
Remco
#2 Posted : Monday, December 19, 2011 10:58:30 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,975

Thanks: 929 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi Sam,

Thanks for posting. Does it make any difference if you turn off the IncludeStaticReferencesInWorkspace setting for the project exhibiting the build error?
Back to top
MetaSam
#3 Posted : Tuesday, December 20, 2011 1:56:41 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/7/2011(UTC)
Posts: 7

Was thanked: 1 time(s) in 1 post(s)
Remco;782 wrote:
Does it make any difference if you turn off the IncludeStaticReferencesInWorkspace setting for the project exhibiting the build error?


Nope, I get the same error.
Back to top
Remco
#4 Posted : Tuesday, December 20, 2011 8:52:13 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,975

Thanks: 929 times
Was thanked: 1257 time(s) in 1170 post(s)
Ok - I have a feeling that this is due to an assembly referencing issue. Would you be able to submit a bug report after you have the build error?
Back to top
Remco
#5 Posted : Monday, December 26, 2011 12:20:05 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,975

Thanks: 929 times
Was thanked: 1257 time(s) in 1170 post(s)
Thanks for sending through the bug report. I'm wondering if you might be able to help me by providing a little more information about the type you are having trouble resolving.

Is it referenced directly from a .dll file? Or is it within a project held within your solution?

Is there anything that could be considered 'interesting' or different about this reference compared with others in your solution? For example, does it make use of an assembly reference alias, or COM? Are you relying on any special build steps around the reference? I.e. 3rd party AOP frameworks, IL merge+manipulation, etc.

Is this the first time that you've used NCrunch? Or did this project work on any previous version?

Finally, does it make any difference if you disable instrumentation (in your NCrunch configuration) for all the projects in your solution?
Back to top
MetaSam
#6 Posted : Wednesday, December 28, 2011 5:01:02 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/7/2011(UTC)
Posts: 7

Was thanked: 1 time(s) in 1 post(s)
I know what the real issue is... We have two projects with the same name (one of them in a subfolder), but different namespaces. NCrunch seems to ignore the second one. That would explain why the reference to types inside those projects can't be found.

Renaming projects so that they all have distinct names fixed the issue.
Back to top
Remco
#7 Posted : Thursday, December 29, 2011 3:38:35 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,975

Thanks: 929 times
Was thanked: 1257 time(s) in 1170 post(s)
Interesting. Thanks for letting me know. I'm sure this is quite a rare case but I'll see what I can do about supporting it in a future revision.
Back to top
MetaSam
#8 Posted : Thursday, December 29, 2011 1:58:58 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/7/2011(UTC)
Posts: 7

Was thanked: 1 time(s) in 1 post(s)
Remco;818 wrote:
Interesting. Thanks for letting me know. I'm sure this is quite a rare case but I'll see what I can do about supporting it in a future revision.


Yes, I'm sure too ;-)

We might just rename those projects to make it work with NCrunch. Thanks for the great support and good work!
Back to top
1 user thanked MetaSam for this useful post.
Remco on 12/29/2011(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.048 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download