Sambathraj
Wed Apr 13 10:44:53 CDT 2005
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" <anon@microsoft.com> wrote in message
news:OVPuaqBQFHA.2000@TK2MSFTNGP15.phx.gbl...
> 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" <Carolina@discussions.microsoft.com> wrote in message
> news:39A8179F-160F-4FE6-A45E-7EEC27E5BAFB@microsoft.com...
>> 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 [MVP C#]" wrote:
>>
>> > 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" <Amataz@discussions.microsoft.com> wrote in message
>> > news:02AC0C92-B63B-473E-AEB3-1530EE1F01FA@microsoft.com...
>> > > Hi all
>> > >
>> > > The point is ...
>> > >
>> > > We all know this is a problem. Has anyone ever been able to solve
>> > > this
>> > > issue?
>> > >
>> >
>> >
>> >
>
>