I have an ASP.NET web site which references a library assembly. As soon as I change something in that library, R# does not recognize any types defined in that library. All symbols are red and intellisense does not show types from the library.
Only restarting VS2005 fixes it again, but restarting VS after every build is unacceptable.
Is this a known issue?
Patrick
Rebuilding the complete solution also fixes it. Saves me about 20 restarts a day.
as far as I remember some events (like assembly reference change notifications) from VS only get raised when the user rebuilds the solution. This may be the key to the problem you're experiencing. Unfortunately the best person who can answer to your post is currently on vacation.
>> I have an ASP.NET web site which references a library assembly. >> As soon as I change something in that library, R# does not recognize >> any >> types defined in that library. >> All symbols are red and intellisense does not show types from the >> library. >> Only restarting VS2005 fixes it again, but restarting VS after every >> build is unacceptable. >> >> Is this a known issue? >> >> Patrick >>
Rebuilding the complete solution also fixes it. Saves me about 20 restarts a day.
I am also seeing this problem in build 256. I recently upgraded from 253, and it wasn't happening in that build. Has this been fixed for 257, it is quite a productivity killer.
as far as I remember some events (like assembly reference change notifications) from VS only get raised when the user rebuilds the solution. This may be the key to the problem you're experiencing. Unfortunately the best person who can answer to your post is currently on vacation.
> >> Patrick schreef: >> >>> I have an ASP.NET web site which references a library assembly. >>> As soon as I change something in that library, R# does not recognize >>> any >>> types defined in that library. >>> All symbols are red and intellisense does not show types from the >>> library. >>> Only restarting VS2005 fixes it again, but restarting VS after every >>> build is unacceptable. >>> >>> Is this a known issue? >>> >>> Patrick >>> >> Rebuilding the complete solution also fixes it. Saves me about 20 >> restarts a day. >> >
I am also seeing this problem in build 256. I recently upgraded from 253, and it wasn't happening in that build. Has this been fixed for 257, it is quite a productivity killer.
>> Hello Patrick, >> >> as far as I remember some events (like assembly reference change >> notifications) from VS only get raised when the user >> rebuilds the solution. This may be the key to the problem you're >> experiencing. Unfortunately the best person who can answer >> to your post is currently on vacation. >> Regards, >> Dmitry Shaporenkov >> JetBrains, Inc >> http://www.jetbrains.com >> "Develop with pleasure!" >>> Patrick schreef: >>> >>>> I have an ASP.NET web site which references a library assembly. >>>> As soon as I change something in that library, R# does not >>>> recognize >>>> any >>>> types defined in that library. >>>> All symbols are red and intellisense does not show types from the >>>> library. >>>> Only restarting VS2005 fixes it again, but restarting VS after >>>> every >>>> build is unacceptable. >>>> Is this a known issue? >>>> >>>> Patrick >>>> >>> Rebuilding the complete solution also fixes it. Saves me about 20 >>> restarts a day. >>>
How do You reference the assembly? Do You copy it manually to the bin folder of the website, or You set path to it via web.config, or it is just a reference with auto-update? If the latter, then we really cannot get notification until VS copies new version of the assembly to the bin folder. That occurs after rebuild or when VS update thread manages to do that, but the time of it is unpredictable.
I am also experiencing this issue, and I do have it set to just be a reference with auto-update. Until 256, I was able to make changes in the class library, and R# would detect them without a problem. (and I get errors later when I realize I didn't build the class library) After building the library, the new version would be updated in the web project. I was perfecly satisfied by this functionality.
The problem now is that when I build the class library, instead of the referenced library being updated, it seems to become invalid, and R# highlights every member from the class library as an error (not found). Even though I can build and execute the web page without any problems.
This was working fine prior to 256, what changed?
I hope this helps you find a solution. Let me know if you have any questions; I'd be happy to help in any way I can.
How do You reference the assembly? Do You copy it manually to the bin folder of the website, or You set path to it via web.config, or it is just a reference with auto-update? If the latter, then we really cannot get notification until VS copies new version of the assembly to the bin folder. That occurs after rebuild or when VS update thread manages to do that, but the time of it is unpredictable.
it would be helpful if you provide us with the ReSharper log (ReSharper | Show Log) captured after the changes were made to an assembly which ReSharper hasn't recognized. Also, please specify the name of the referenced assembly, so that we can locate it in the log. Thanks.
> >> Sergey, >> >> I am also experiencing this issue, and I do have it set to just be a >> reference with auto-update. Until 256, I was able to make changes in >> the class library, and R# would detect them without a problem. (and I >> get errors later when I realize I didn't build the class library) >> After building the library, the new version would be updated in the >> web project. I was perfecly satisfied by this functionality. >> >> The problem now is that when I build the class library, instead of >> the referenced library being updated, it seems to become invalid, and >> R# highlights every member from the class library as an error (not >> found). Even though I can build and execute the web page without any >> problems. >> >> This was working fine prior to 256, what changed? >> >> I hope this helps you find a solution. Let me know if you have any >> questions; I'd be happy to help in any way I can. >> >> Randy >> >> "Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message >> news:ebpv5i$ec1$1@is.intellij.net... >> >>> Patrick, >>> >>> How do You reference the assembly? Do You copy it manually to the bin >>> folder of the website, or You set path to it via web.config, or it is >>> just a reference with auto-update? If the latter, then we really >>> cannot get notification until VS copies new version of the assembly >>> to the bin folder. That occurs after rebuild or when VS update thread >>> manages to do that, but the time of it is unpredictable. >>> >>> -- >>> Sergey V. Coox >>> JetBrains, Inc >>> http://www.jetbrains.com >>> "Develop with pleasure!" >
Does it still exists in 258? I had this issue and had to go back to 248. Thanks
"Patrick" <Patrick@nospam.spam> wrote in message news:eapr97$hq1$1@is.intellij.net... >I have an ASP.NET web site which references a library assembly.
As soon as I change something in that library, R# does not recognize any types defined in that library. All symbols are red and intellisense does not show types from the library.
>
Only restarting VS2005 fixes it again, but restarting VS after every build is unacceptable.
according to the log ReSharper received a notification about external change of the assembly C:\Project Files\Solutions\BlueSkyLeagues\BlueSkyLeague\bin\Debug\BlueSkyLeague.dll and hence it must have re-loaded it. Could you please also tell me in what project the reference to this assembly got lost after re-compiling the assembly? And was that reference an assembly reference or a reference to the BlueSkyLeague project for which the assembly is the output Dll? Thanks.
>> Hello Randy, >> >> it would be helpful if you provide us with the ReSharper log >> (ReSharper | >> Show Log) captured after the changes were made to >> an assembly which ReSharper hasn't recognized. Also, please specify >> the >> name >> of the referenced assembly, so that we can >> locate it in the log. Thanks. >> Regards, >> Dmitry Shaporenkov >> JetBrains, Inc >> http://www.jetbrains.com >> "Develop with pleasure!" >>> Sergey, >>> >>> I am also experiencing this issue, and I do have it set to just be a >>> reference with auto-update. Until 256, I was able to make changes >>> in the class library, and R# would detect them without a problem. >>> (and I get errors later when I realize I didn't build the class >>> library) After building the library, the new version would be >>> updated in the web project. I was perfecly satisfied by this >>> functionality. >>> >>> The problem now is that when I build the class library, instead of >>> the referenced library being updated, it seems to become invalid, >>> and R# highlights every member from the class library as an error >>> (not found). Even though I can build and execute the web page >>> without any problems. >>> >>> This was working fine prior to 256, what changed? >>> >>> I hope this helps you find a solution. Let me know if you have any >>> questions; I'd be happy to help in any way I can. >>> >>> Randy >>> >>> "Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message >>> news:ebpv5i$ec1$1@is.intellij.net... >>> >>>> Patrick, >>>> >>>> How do You reference the assembly? Do You copy it manually to the >>>> bin folder of the website, or You set path to it via web.config, or >>>> it is just a reference with auto-update? If the latter, then we >>>> really cannot get notification until VS copies new version of the >>>> assembly to the bin folder. That occurs after rebuild or when VS >>>> update thread manages to do that, but the time of it is >>>> unpredictable. >>>> >>>> -- >>>> Sergey V. Coox >>>> JetBrains, Inc >>>> http://www.jetbrains.com >>>> "Develop with pleasure!"
>>I have an ASP.NET web site which references a library assembly. >> As soon as I change something in that library, R# does not recognize any >> types defined in that library. >> All symbols are red and intellisense does not show types from the >> library. >> >> Only restarting VS2005 fixes it again, but restarting VS after every >> build is unacceptable. >> >> Is this a known issue? >> >> Patrick >> >
Patrick schreef:
Rebuilding the complete solution also fixes it. Saves me about 20
restarts a day.
Hello Patrick,
as far as I remember some events (like assembly reference change notifications)
from VS only get raised when the user
rebuilds the solution. This may be the key to the problem you're experiencing.
Unfortunately the best person who can answer
to your post is currently on vacation.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> I have an ASP.NET web site which references a library assembly.
>> As soon as I change something in that library, R# does not recognize
>> any
>> types defined in that library.
>> All symbols are red and intellisense does not show types from the
>> library.
>> Only restarting VS2005 fixes it again, but restarting VS after every
>> build is unacceptable.
>>
>> Is this a known issue?
>>
>> Patrick
>>
Dmitry,
I am also seeing this problem in build 256. I recently upgraded from 253,
and it wasn't happening in that build. Has this been fixed for 257, it is
quite a productivity killer.
Thanks.
Randy
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91b67f38c88515ec80ae8a@news.intellij.net...
>
>
>
>
>
>> Patrick schreef:
>>
>>> I have an ASP.NET web site which references a library assembly.
>>> As soon as I change something in that library, R# does not recognize
>>> any
>>> types defined in that library.
>>> All symbols are red and intellisense does not show types from the
>>> library.
>>> Only restarting VS2005 fixes it again, but restarting VS after every
>>> build is unacceptable.
>>>
>>> Is this a known issue?
>>>
>>> Patrick
>>>
>> Rebuilding the complete solution also fixes it. Saves me about 20
>> restarts a day.
>>
>
Hello Randy,
do you mean that ReSharper becomes aware of your changes only after you rebuild
the solution? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Hello Patrick,
>>
>> as far as I remember some events (like assembly reference change
>> notifications) from VS only get raised when the user
>> rebuilds the solution. This may be the key to the problem you're
>> experiencing. Unfortunately the best person who can answer
>> to your post is currently on vacation.
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Patrick schreef:
>>>
>>>> I have an ASP.NET web site which references a library assembly.
>>>> As soon as I change something in that library, R# does not
>>>> recognize
>>>> any
>>>> types defined in that library.
>>>> All symbols are red and intellisense does not show types from the
>>>> library.
>>>> Only restarting VS2005 fixes it again, but restarting VS after
>>>> every
>>>> build is unacceptable.
>>>> Is this a known issue?
>>>>
>>>> Patrick
>>>>
>>> Rebuilding the complete solution also fixes it. Saves me about 20
>>> restarts a day.
>>>
Patrick,
How do You reference the assembly? Do You copy it manually to the bin folder
of the website, or You set path to it via web.config, or it is just a
reference with auto-update? If the latter, then we really cannot get
notification until VS copies new version of the assembly to the bin folder.
That occurs after rebuild or when VS update thread manages to do that, but
the time of it is unpredictable.
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Sergey,
I am also experiencing this issue, and I do have it set to just be a
reference with auto-update. Until 256, I was able to make changes in the
class library, and R# would detect them without a problem. (and I get errors
later when I realize I didn't build the class library) After building the
library, the new version would be updated in the web project. I was perfecly
satisfied by this functionality.
The problem now is that when I build the class library, instead of the
referenced library being updated, it seems to become invalid, and R#
highlights every member from the class library as an error (not found). Even
though I can build and execute the web page without any problems.
This was working fine prior to 256, what changed?
I hope this helps you find a solution. Let me know if you have any
questions; I'd be happy to help in any way I can.
Randy
"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
news:ebpv5i$ec1$1@is.intellij.net...
>
>
Dmitry,
I have attached the ReSharper Log.
I compiled my assembly: BlueSkyLeague.dll, waited a few seconds, and
resharper refreshed losing the reference to the assembly.
I hope it helps. Let me know if you have any questions.
Randy
"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91b68e98c88e628b00d990@news.intellij.net...
>
>
>
>
>> Sergey,
>>
>> I am also experiencing this issue, and I do have it set to just be a
>> reference with auto-update. Until 256, I was able to make changes in
>> the class library, and R# would detect them without a problem. (and I
>> get errors later when I realize I didn't build the class library)
>> After building the library, the new version would be updated in the
>> web project. I was perfecly satisfied by this functionality.
>>
>> The problem now is that when I build the class library, instead of
>> the referenced library being updated, it seems to become invalid, and
>> R# highlights every member from the class library as an error (not
>> found). Even though I can build and execute the web page without any
>> problems.
>>
>> This was working fine prior to 256, what changed?
>>
>> I hope this helps you find a solution. Let me know if you have any
>> questions; I'd be happy to help in any way I can.
>>
>> Randy
>>
>> "Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
>> news:ebpv5i$ec1$1@is.intellij.net...
>>
>>> Patrick,
>>>
>>> How do You reference the assembly? Do You copy it manually to the bin
>>> folder of the website, or You set path to it via web.config, or it is
>>> just a reference with auto-update? If the latter, then we really
>>> cannot get notification until VS copies new version of the assembly
>>> to the bin folder. That occurs after rebuild or when VS update thread
>>> manages to do that, but the time of it is unpredictable.
>>>
>>> --
>>> Sergey V. Coox
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>
Attachment(s):
Resharper081706.log
Does it still exists in 258? I had this issue and had to go back to 248.
Thanks
"Patrick" <Patrick@nospam.spam> wrote in message
news:eapr97$hq1$1@is.intellij.net...
>I have an ASP.NET web site which references a library assembly.
>
>
>
Hello Randy,
according to the log ReSharper received a notification about external change
of the assembly
C:\Project Files\Solutions\BlueSkyLeagues\BlueSkyLeague\bin\Debug\BlueSkyLeague.dll
and hence it must have re-loaded it.
Could you please also tell me in what project the reference to this assembly
got lost after re-compiling the assembly? And was
that reference an assembly reference or a reference to the BlueSkyLeague
project for which the assembly is the
output Dll? Thanks.
Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
>> Hello Randy,
>>
>> it would be helpful if you provide us with the ReSharper log
>> (ReSharper |
>> Show Log) captured after the changes were made to
>> an assembly which ReSharper hasn't recognized. Also, please specify
>> the
>> name
>> of the referenced assembly, so that we can
>> locate it in the log. Thanks.
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Sergey,
>>>
>>> I am also experiencing this issue, and I do have it set to just be a
>>> reference with auto-update. Until 256, I was able to make changes
>>> in the class library, and R# would detect them without a problem.
>>> (and I get errors later when I realize I didn't build the class
>>> library) After building the library, the new version would be
>>> updated in the web project. I was perfecly satisfied by this
>>> functionality.
>>>
>>> The problem now is that when I build the class library, instead of
>>> the referenced library being updated, it seems to become invalid,
>>> and R# highlights every member from the class library as an error
>>> (not found). Even though I can build and execute the web page
>>> without any problems.
>>>
>>> This was working fine prior to 256, what changed?
>>>
>>> I hope this helps you find a solution. Let me know if you have any
>>> questions; I'd be happy to help in any way I can.
>>>
>>> Randy
>>>
>>> "Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
>>> news:ebpv5i$ec1$1@is.intellij.net...
>>>
>>>> Patrick,
>>>>
>>>> How do You reference the assembly? Do You copy it manually to the
>>>> bin folder of the website, or You set path to it via web.config, or
>>>> it is just a reference with auto-update? If the latter, then we
>>>> really cannot get notification until VS copies new version of the
>>>> assembly to the bin folder. That occurs after rebuild or when VS
>>>> update thread manages to do that, but the time of it is
>>>> unpredictable.
>>>>
>>>> --
>>>> Sergey V. Coox
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
Shimon,
Yes, this problem still exists in 258, I believe it was introduced in 256.
Randy
"Shimon Sim" <shimonsim048@community.nospam> wrote in message
news:ec3aa6$477$1@is.intellij.net...
>
>>I have an ASP.NET web site which references a library assembly.
>> As soon as I change something in that library, R# does not recognize any
>> types defined in that library.
>> All symbols are red and intellisense does not show types from the
>> library.
>>
>> Only restarting VS2005 fixes it again, but restarting VS after every
>> build is unacceptable.
>>
>> Is this a known issue?
>>
>> Patrick
>>
>