God why can't anyone help me???!!!

[Guest]

I can't beleive that I'm the only one in the world to run into this, especially since it's SO duplicateable and seems to be impossible to overcome once it starts. This is my second post today on this subject, my third post on this issue as a whole, as it's happened a couple of different times now with different projects. Below is the text of my original message, and I would REALLY appreciate any advice on what mgiht POSSIBLY be the CAUSE of this and HOW to FIX it!!!!

Update... In addition to the information below, I have also tried building project "A", and then referencing it from a new project in a diferent solution in a diferent IDE instance... It still locks up the IDE as soon as I choose one of the affected functions from the intellisense dropdown. Again, there seems to be no PATTERN to which functions are affected, although once it starts it won't stop no matter what I do...

Original post...

I am having a peculiar problem with lockups in the VS environment. It does not happen often, but when it does, it seems to break my entire solution / project, and I don't know what to do to fix it. I have (as usual) a theory on where the cause might lie, however I lack the intimate knowledge of the file / project structure of .NET apps to research it any farther (not to mention the fact that I already have deadlines I'm under)... Anyway, here is the gist of what's wrong..

I have a multi-project solution that I'm developing. In project "A", I define a class and a bunch of static functions (for data access, although I don't think that the actual use is really all that relevant). In project "B", my business tier, I call out to functions in the data access layer (project "A"). When I am typing in project "B", and type the name of a class in project "A", followed by the period, I get the intellisense drop-down, with all the fxns in it. I can scroll through the list and choose one, but as soon as I choose one (either by clicking on it, or hitting the ENTER or "(" key to allow AutoComplete to complete the entry, my Visual Studio session locks up completely

I can force the IDE closed, but I end up losing any changes in any unsaved projects. This does not happen with ALL of the functions in that class, but at least one of them, and it happens every single time I try to use it, so it's not a random occurrence. This has happened with other projects before. Even when I restart VS, the same thing will again occur when I try to use that fxn. The only workaround that I have found is to go into project "A" and change the name of the function. Then, the problem goes away. If, however i change it back to its original name, the problem comes back. I know of nothing particularly unusual with regard to the names I've choses for the classes or fxns

I have a theory (JUST a theory), based on my experience with MFC and VS 6... Sometimes the class wizard would get screwed up and your dropdowns would quit working. The way to fix this in the project was to exit and delete the .NCB file for that project. Somtimes, if it got screwed up enough, you could go and manually edit the .CLW file and fix whatever was wrong, and the class wizard would again begin to work. I am guessing that since this problem I am having comes and goes as the name of the function changes, that "something" "somewhere" (how's that for a nice technical explanation?) is screwed up with respect to the confguration of the project. As this is stuff going into a production environment, it's really not acceptable for me to just start randomly deleting files and trying to re-create them, nor is it appropriate for me to hack around with the project files and experiement until I find what works. Due to our naming conventions and design standards, simply renaming functions to avoid this error is also not really acceptable

I would VERY MUCH appreicate any help anyone can give me on this, or at least some ideas or insight on what to try, as this is really maknig it difficult for me to work on this project when it starts doing this. Thank you very much in advance. :

JIM

 

[Willy Denoyette [MVP]]

I can't beleive that I'm the only one in the world to run into this,
especially since it's SO duplicateable and seems to be impossible to
overcome once it starts. This is my second post today on this subject, my
third post on this issue as a whole, as it's happened a couple of different
times now with different projects. Below is the text of my original
message, and I would REALLY appreciate any advice on what mgiht POSSIBLY be
the CAUSE of this and HOW to FIX it!!!!!

Update... In addition to the information below, I have also tried
building project "A", and then referencing it from a new project in a
diferent solution in a diferent IDE instance... It still locks up the IDE
as soon as I choose one of the affected functions from the intellisense
dropdown. Again, there seems to be no PATTERN to which functions are
affected, although once it starts it won't stop no matter what I do....

I sure you might find better help in "microsoft.public.vsnet.ide".

Willy.

 

[Louis Marascio]

You can try to delete the <projectname>.projdata files for your
projects. They live in the "obj" directory. This sometimes gives
Intellisense the swift kick in the rear end that it needs to get back
onto the right track.

Louis

--
Louis Marascio
louis at no spam dot louismarascio dot com

I can't beleive that I'm the only one in the world to run into this,

especially since it's SO duplicateable and seems to be impossible to
overcome once it starts. This is my second post today on this
subject, my third post on this issue as a whole, as it's happened a
couple of different times now with different projects. Below is the
text of my original message, and I would REALLY appreciate any advice
on what mgiht POSSIBLY be the CAUSE of this and HOW to FIX it!!!!!

Update... In addition to the information below, I have also tried

building project "A", and then referencing it from a new project in a
diferent solution in a diferent IDE instance... It still locks up the
IDE as soon as I choose one of the affected functions from the
intellisense dropdown. Again, there seems to be no PATTERN to which
functions are affected, although once it starts it won't stop no
matter what I do....

Original post....

I am having a peculiar problem with lockups in the VS environment.

It does not happen often, but when it does, it seems to break my
entire solution / project, and I don't know what to do to fix it. I
have (as usual) a theory on where the cause might lie, however I lack
the intimate knowledge of the file / project structure of .NET apps to
research it any farther (not to mention the fact that I already have
deadlines I'm under)... Anyway, here is the gist of what's wrong...

I have a multi-project solution that I'm developing. In project

"A", I define a class and a bunch of static functions (for data
access, although I don't think that the actual use is really all that
relevant). In project "B", my business tier, I call out to functions
in the data access layer (project "A"). When I am typing in project
"B", and type the name of a class in project "A", followed by the
period, I get the intellisense drop-down, with all the fxns in it. I
can scroll through the list and choose one, but as soon as I choose
one (either by clicking on it, or hitting the ENTER or "(" key to
allow AutoComplete to complete the entry, my Visual Studio session
locks up completely.

I can force the IDE closed, but I end up losing any changes in any

unsaved projects. This does not happen with ALL of the functions in
that class, but at least one of them, and it happens every single time
I try to use it, so it's not a random occurrence. This has happened
with other projects before. Even when I restart VS, the same thing
will again occur when I try to use that fxn. The only workaround that
I have found is to go into project "A" and change the name of the
function. Then, the problem goes away. If, however i change it back
to its original name, the problem comes back. I know of nothing
particularly unusual with regard to the names I've choses for the
classes or fxns.

I have a theory (JUST a theory), based on my experience with MFC and

VS 6... Sometimes the class wizard would get screwed up and your
dropdowns would quit working. The way to fix this in the project was
to exit and delete the .NCB file for that project. Somtimes, if it
got screwed up enough, you could go and manually edit the .CLW file
and fix whatever was wrong, and the class wizard would again begin to
work. I am guessing that since this problem I am having comes and
goes as the name of the function changes, that "something" "somewhere"
(how's that for a nice technical explanation?) is screwed up with
respect to the confguration of the project. As this is stuff going
into a production environment, it's really not acceptable for me to
just start randomly deleting files and trying to re-create them, nor
is it appropriate for me to hack around with the project files and
experiement until I find what works. Due to our naming conventions
and design standards, simply renaming functions to avoid this error is
also not really acceptable.

I would VERY MUCH appreicate any help anyone can give me on this, or

at least some ideas or insight on what to try, as this is really
maknig it difficult for me to work on this project when it starts
doing this. Thank you very much in advance.

 

[Stoitcho Goutsev \(100\) [C# MVP]]

Hi Jim,
It's never happened to me.
Have you tried those names in a test project simply to check if the names
are the problem?
Can you post the prototypes of the methods you have problem with. At least I
can try it to see if I get the same.

--
B\rgds
100 [C# MVP]

I can't beleive that I'm the only one in the world to run into this,

especially since it's SO duplicateable and seems to be impossible to
overcome once it starts. This is my second post today on this subject, my
third post on this issue as a whole, as it's happened a couple of different
times now with different projects. Below is the text of my original
message, and I would REALLY appreciate any advice on what mgiht POSSIBLY be
the CAUSE of this and HOW to FIX it!!!!!

Update... In addition to the information below, I have also tried

building project "A", and then referencing it from a new project in a
diferent solution in a diferent IDE instance... It still locks up the IDE as
soon as I choose one of the affected functions from the intellisense
dropdown. Again, there seems to be no PATTERN to which functions are
affected, although once it starts it won't stop no matter what I do....

Original post....

I am having a peculiar problem with lockups in the VS environment. It

does not happen often, but when it does, it seems to break my entire
solution / project, and I don't know what to do to fix it. I have (as
usual) a theory on where the cause might lie, however I lack the intimate
knowledge of the file / project structure of .NET apps to research it any
farther (not to mention the fact that I already have deadlines I'm under)...
Anyway, here is the gist of what's wrong...

I have a multi-project solution that I'm developing. In project "A", I

define a class and a bunch of static functions (for data access, although I
don't think that the actual use is really all that relevant). In project "B
", my business tier, I call out to functions in the data access layer
(project "A"). When I am typing in project "B", and type the name of a
class in project "A", followed by the period, I get the intellisense
drop-down, with all the fxns in it. I can scroll through the list and
choose one, but as soon as I choose one (either by clicking on it, or
hitting the ENTER or "(" key to allow AutoComplete to complete the entry, my
Visual Studio session locks up completely.

I can force the IDE closed, but I end up losing any changes in any unsaved

projects. This does not happen with ALL of the functions in that class, but
at least one of them, and it happens every single time I try to use it, so
it's not a random occurrence. This has happened with other projects before.
Even when I restart VS, the same thing will again occur when I try to use
that fxn. The only workaround that I have found is to go into project "A"
and change the name of the function. Then, the problem goes away. If,
however i change it back to its original name, the problem comes back. I
know of nothing particularly unusual with regard to the names I've choses
for the classes or fxns.

I have a theory (JUST a theory), based on my experience with MFC and VS

6... Sometimes the class wizard would get screwed up and your dropdowns
would quit working. The way to fix this in the project was to exit and
delete the .NCB file for that project. Somtimes, if it got screwed up
enough, you could go and manually edit the .CLW file and fix whatever was
wrong, and the class wizard would again begin to work. I am guessing that
since this problem I am having comes and goes as the name of the function
changes, that "something" "somewhere" (how's that for a nice technical
explanation?) is screwed up with respect to the confguration of the project.
As this is stuff going into a production environment, it's really not
acceptable for me to just start randomly deleting files and trying to
re-create them, nor is it appropriate for me to hack around with the project
files and experiement until I find what works. Due to our naming
conventions and design standards, simply renaming functions to avoid this
error is also not really acceptable.

I would VERY MUCH appreicate any help anyone can give me on this, or at

least some ideas or insight on what to try, as this is really maknig it
difficult for me to work on this project when it starts doing this. Thank
you very much in advance.

 

[Louis Marascio]

Try going into your 'obj' directory under your project, and deleting
the <projectname>.projdata files. They are hidden, so un-hide them
first.

Louis

--
Louis Marascio
louis at no spam dot louismarascio dot com

I can't beleive that I'm the only one in the world to run into this,

especially since it's SO duplicateable and seems to be impossible to
overcome once it starts. This is my second post today on this
subject, my third post on this issue as a whole, as it's happened a
couple of different times now with different projects. Below is the
text of my original message, and I would REALLY appreciate any advice
on what mgiht POSSIBLY be the CAUSE of this and HOW to FIX it!!!!!

Update... In addition to the information below, I have also tried

building project "A", and then referencing it from a new project in a
diferent solution in a diferent IDE instance... It still locks up the
IDE as soon as I choose one of the affected functions from the
intellisense dropdown. Again, there seems to be no PATTERN to which
functions are affected, although once it starts it won't stop no
matter what I do....

Original post....

I am having a peculiar problem with lockups in the VS environment.

It does not happen often, but when it does, it seems to break my
entire solution / project, and I don't know what to do to fix it. I
have (as usual) a theory on where the cause might lie, however I lack
the intimate knowledge of the file / project structure of .NET apps to
research it any farther (not to mention the fact that I already have
deadlines I'm under)... Anyway, here is the gist of what's wrong...

I have a multi-project solution that I'm developing. In project

"A", I define a class and a bunch of static functions (for data
access, although I don't think that the actual use is really all that
relevant). In project "B", my business tier, I call out to functions
in the data access layer (project "A"). When I am typing in project
"B", and type the name of a class in project "A", followed by the
period, I get the intellisense drop-down, with all the fxns in it. I
can scroll through the list and choose one, but as soon as I choose
one (either by clicking on it, or hitting the ENTER or "(" key to
allow AutoComplete to complete the entry, my Visual Studio session
locks up completely.

I can force the IDE closed, but I end up losing any changes in any

unsaved projects. This does not happen with ALL of the functions in
that class, but at least one of them, and it happens every single time
I try to use it, so it's not a random occurrence. This has happened
with other projects before. Even when I restart VS, the same thing
will again occur when I try to use that fxn. The only workaround that
I have found is to go into project "A" and change the name of the
function. Then, the problem goes away. If, however i change it back
to its original name, the problem comes back. I know of nothing
particularly unusual with regard to the names I've choses for the
classes or fxns.

I have a theory (JUST a theory), based on my experience with MFC and

VS 6... Sometimes the class wizard would get screwed up and your
dropdowns would quit working. The way to fix this in the project was
to exit and delete the .NCB file for that project. Somtimes, if it
got screwed up enough, you could go and manually edit the .CLW file
and fix whatever was wrong, and the class wizard would again begin to
work. I am guessing that since this problem I am having comes and
goes as the name of the function changes, that "something" "somewhere"
(how's that for a nice technical explanation?) is screwed up with
respect to the confguration of the project. As this is stuff going
into a production environment, it's really not acceptable for me to
just start randomly deleting files and trying to re-create them, nor
is it appropriate for me to hack around with the project files and
experiement until I find what works. Due to our naming conventions
and design standards, simply renaming functions to avoid this error is
also not really acceptable.

I would VERY MUCH appreicate any help anyone can give me on this, or

at least some ideas or insight on what to try, as this is really
maknig it difficult for me to work on this project when it starts
doing this. Thank you very much in advance.