Annoyance: Intellisense doesn't work for referenced typed datasets?

  • Thread starter Thread starter Mike Edenfield
  • Start date Start date
M

Mike Edenfield

Does anyone know why Intellisense frequently stops working for strongly
typed datasets when the dataset is in a referenced assembly? Within the
assembly where I have the dataset, it works fine, but outside of that
assembly I can rarely get Intellisense to recognize anything beyond the
dataset type itself.

That is, it will pick up "TypedDataSet" but not "TypedDataSet.TypedRow"
nor "typedDataSetInstance.TableName".

??

--Mike
 
Hi all

The point is ...

We all know this is a problem. Has anyone ever been able to solve this issue?
 
Did you try closing vs.net, delete obj folder and restart vs.net?
Btw, I am blindly guessing here as I (like Sahil) don't see the original
message...
 
Hi!

I get this from time to time as well. It seems to me that rebuilding my
solution helps. My guess: if you've changed something in the referenced
assembly, the solution knows this and needs to recompile the projects to get
the latest version of the reference.


Original post was made by Mike in MSDN newsgroup:
---------------------------------
Does anyone know why Intellisense frequently stops working for strongly
typed datasets when the dataset is in a referenced assembly? Within the
assembly where I have the dataset, it works fine, but outside of that
assembly I can rarely get Intellisense to recognize anything beyond the
dataset type itself.

That is, it will pick up "TypedDataSet" but not "TypedDataSet.TypedRow"
nor "typedDataSetInstance.TableName".

??

--Mike
-------------------------------------------


Miha Markic said:
Did you try closing vs.net, delete obj folder and restart vs.net?
Btw, I am blindly guessing here as I (like Sahil) don't see the original
message...

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
SLODUG - Slovene Developer Users Group
www.rthand.com

Amataz said:
Hi all

The point is ...

We all know this is a problem. Has anyone ever been able to solve this
issue?
Click to expand...
Click to expand...
 
This has been bugging us for a long time to the extent we call it
'intellifish' (ie memory of a goldfish ;o). It also tends to forget enum
types in classes as well... We have 100 projects in our main solution so a
reload is very costly. I've found this solution works without a reload (of
even the project) -

Note if you get any file locks at any stage of the process, you WILL have to
restart :( This is a whole other can of worms :)

1) In the project, delete all the files in the obj directory tree (keep
'Debug','Release' and the 'Temp' and 'TempPE' folders inside them, just wipe
the files)
2) Delete all the files in the bin directory
3) Update web reference
4) Rebuild project and hopefully the intellisense will come back...

The intellisense also seems to get confused when two datasets have the same
table name, go to reference will often jump to the wrong reference.cs...

HTH

Simon


Carolina said:
Hi!

I get this from time to time as well. It seems to me that rebuilding my
solution helps. My guess: if you've changed something in the referenced
assembly, the solution knows this and needs to recompile the projects to get
the latest version of the reference.


Original post was made by Mike in MSDN newsgroup:
---------------------------------
Does anyone know why Intellisense frequently stops working for strongly
typed datasets when the dataset is in a referenced assembly? Within the
assembly where I have the dataset, it works fine, but outside of that
assembly I can rarely get Intellisense to recognize anything beyond the
dataset type itself.

That is, it will pick up "TypedDataSet" but not "TypedDataSet.TypedRow"
nor "typedDataSetInstance.TableName".

??

--Mike
-------------------------------------------


Miha Markic said:
Did you try closing vs.net, delete obj folder and restart vs.net?
Btw, I am blindly guessing here as I (like Sahil) don't see the original
message...

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
SLODUG - Slovene Developer Users Group
www.rthand.com

Amataz said:
Hi all

The point is ...

We all know this is a problem. Has anyone ever been able to solve this
issue?
Click to expand...
Click to expand...
Click to expand...
 
Hi,
It also some times heppens to me. Closing the solution (not closing the dev
enviroment) will help. This will make the studio to refresh its reference
related data.
Regards,
Sambathraj

Anonymous Poster said:
This has been bugging us for a long time to the extent we call it
'intellifish' (ie memory of a goldfish ;o). It also tends to forget enum
types in classes as well... We have 100 projects in our main solution so a
reload is very costly. I've found this solution works without a reload (of
even the project) -

Note if you get any file locks at any stage of the process, you WILL have
to
restart :( This is a whole other can of worms :)

1) In the project, delete all the files in the obj directory tree (keep
'Debug','Release' and the 'Temp' and 'TempPE' folders inside them, just
wipe
the files)
2) Delete all the files in the bin directory
3) Update web reference
4) Rebuild project and hopefully the intellisense will come back...

The intellisense also seems to get confused when two datasets have the
same
table name, go to reference will often jump to the wrong reference.cs...

HTH

Simon


Carolina said:
Hi!

I get this from time to time as well. It seems to me that rebuilding my
solution helps. My guess: if you've changed something in the referenced
assembly, the solution knows this and needs to recompile the projects to get
the latest version of the reference.


Original post was made by Mike in MSDN newsgroup:
---------------------------------
Does anyone know why Intellisense frequently stops working for strongly
typed datasets when the dataset is in a referenced assembly? Within the
assembly where I have the dataset, it works fine, but outside of that
assembly I can rarely get Intellisense to recognize anything beyond the
dataset type itself.

That is, it will pick up "TypedDataSet" but not "TypedDataSet.TypedRow"
nor "typedDataSetInstance.TableName".

??

--Mike
-------------------------------------------


Miha Markic said:
Did you try closing vs.net, delete obj folder and restart vs.net?
Btw, I am blindly guessing here as I (like Sahil) don't see the
original
message...

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
SLODUG - Slovene Developer Users Group
www.rthand.com

Hi all

The point is ...

We all know this is a problem. Has anyone ever been able to solve
this
issue?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top