VisualBasic.Net: Unknown Entity for existing entities

[Sherry]

I just installed JustCode in my VS2008 environment running .net 3.5 on Windows XP SP3 and I get over 300 errors in my solution stating that there are unknown entities even though the entities exist and my projects compile.

I verified that the inherits properties, namespaces, and Ids are all correct.

[Jordan]

Hi Edward,

Thanks for the feedback. We tested the official version with a lot of internal and external projects and it works for them. Is it possible to send us the sample project with these exceptions to the support ticket?

Best wishes,
Jordan
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[James]

I am having the same problem using Windows 7 and Visual Basic 2010.

[Sherry]

I haven't been able to create a test project for Telerik but I decided that it wasn't worth using for us because it creates so many inaccurate reports that it dilutes any possible indicators.  Telerik is onto something but there needs to be more refinement to the tool.

[Hans Kratz]

Hi Edward, hi James,

 as Jordan said we have an extensive test suite containing a lot of projects, both from in-house work and from external sources (e.g. open source projects), mostly containing C# source code. JustCode does not show any incorrect errors on those projects. Unfortunately our test coverage for VB is not as extensive as for C# because VB.net is not used extensively in-house and there are only a few open source projects containing VB.net source code.

So it would really help us a lot if you could provide us with more details about the false errors JustCode reports. For that a sample solution would be perfect but even the information sent using JustCode's "Report Good Code Red" quick fix (available via Alt-Enter on red underlined code) or posting small code snippets can help.

We are aware that the usefulness of JustCode is greatly diminished by false errors. So be assured that we treat errors in the code analysis with highest priority. 

Sincerely yours,
Hans Kratz
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Sherry]

Hans,
Your response is why I use telerik and recommend it to other colleagues.   You and your team are always responsive and show passion in delivering quality products.

I did uninstall JustCode but I will create a solution for you so that you may see where I seem to be getting these false positives.

Thanks.

[Sherry]

I have attached two screen shots -- the aspx.vb that has the unknown entities underlined and the aspx page with the label controls in them.  I'll try to get you a project.

[Sherry]

I did notice that a lot of these entities are not found when encapsulated by our custom controls, but we do not receive VS errors when they are encapsulated by our custom controls.  Maybe that's the issue.

[mark leavesley]

Hello,

Maybe related, but in VB.NET I had a lot of false errors with class functions not recognised because JustCode didn't like the empty parenthesis on function calls with no parameters:

Class A
function NoParams()
return "fred"
end function
end class

Dim clsA as New A
debug.print A.NoParams() '<< Error in JustCode but not VS
debug.print A.NoParams '<< Fine in JustCode and VS

Bizarrely, it only did it on two of the many functions with no parameters, but it did it on every occurrence. The fix was simple and VS didn't seem to care whether the empty parenthesis was there or not.

I've since uninstalled JustCode as the performance penalty and other bizarre false errors were more a hinderance than a benefit. I've got another set of issues now that I uninstalled it, but that's for another thread.

[Hans Kratz]

Hi Edward,

 thanks for the screenshots. It looks like you have run into a bug in JustCode which is caused by incomplete support for single instance templates: Fields are defined for controls in templates where the property associated with the template is marked with [TemplateInstance(TemplateInstance.Single)]. JustCode does not support this for arbitrary property names right now.

Can you check if this problem is only occurring for fields define within *Template where the associated property is marked with this attribute?

We scheduled this issue to be fixed in the Q2 release of JustCode.

Sincerely yours,
Hans Kratz
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Hans Kratz]

Hi Mark,

I think the problem you experience is caused by a different problem because the sample you provided does not involve ASP.net. Could you check if you still have older versions of your code with which we could reproduce it?

If you do please open a new support ticket or forum post to provide further information about this issue.

Your help in tracking this down is greatly appreciated!


Kind regards,
Hans Kratz
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.