all groups > dotnet general > february 2008 >
You're in the

dotnet general

group:

migarting my appliacation from VS 2003 to VS 2005


migarting my appliacation from VS 2003 to VS 2005 koolquery@gmail.com
2/29/2008 5:38:11 AM
dotnet general:
Hi i;m
migarting my appliacation from VS 2003 to VS 2005
I've coverted it but now i'm getting the error
"Error 1 The type or namespace name 'EncriptDecript' could
not be
found (are you missing a using directive or an assembly
reference?) C:
\Inetpub\wwwroot\ \Login.aspx.cs 14
"
How to rectify it ?

Re: migarting my appliacation from VS 2003 to VS 2005 koolquery@gmail.com
2/29/2008 6:39:41 AM
[quoted text, click to view]

using EncriptDecript.Encript;
this is giving the error and i'm not getting this namespace or where
Re: migarting my appliacation from VS 2003 to VS 2005 koolquery@gmail.com
2/29/2008 6:39:56 AM
[quoted text, click to view]

using EncriptDecript.Encript;
this is giving the error and i'm not getting this namespace or where
RE: migarting my appliacation from VS 2003 to VS 2005 Family Tree Mike
2/29/2008 1:41:00 PM


[quoted text, click to view]

Are you sure on the spelling? EncryptDecrypt comes up in google.
Re: migarting my appliacation from VS 2003 to VS 2005 Jon Skeet [C# MVP]
2/29/2008 1:54:42 PM
[quoted text, click to view]

1) Work out where the type or namespace is meant to come from
2) Make sure you've referenced that assembly

--
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
Re: migarting my appliacation from VS 2003 to VS 2005 Marc Gravell
2/29/2008 1:55:19 PM
Add a reference to wherever EncriptDescript is defined?

Re: migarting my appliacation from VS 2003 to VS 2005 Alex Meleta
2/29/2008 1:56:12 PM
Hi koolquery@gmail.com,

Check that References are the same for both the projects. It seems like you
lost one(s) for some reason during convertion.

Regards, Alex
[TechBlog] http://devkids.blogspot.com

[quoted text, click to view]

Re: migarting my appliacation from VS 2003 to VS 2005 Alex Meleta
2/29/2008 2:45:45 PM
Hi koolquery@gmail.com,

Using the Object Browser track what is the module is responsible for it.
It's not a .NET common assembly, then there should be the link somewhere
in project. Check reference or gac or such to find lost assembly in 2003
project. Then refer it in the new one. There is high possibility that lost
reference link to an assembly or a project in solutiuon cause this exception.

Regards, Alex
[TechBlog] http://devkids.blogspot.com

[quoted text, click to view]

Re: migarting my appliacation from VS 2003 to VS 2005 Jon Skeet [C# MVP]
2/29/2008 3:56:51 PM
[quoted text, click to view]

Well if it was building in VS2003, you must have had it back then...

--
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
AddThis Social Bookmark Button