Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / November 2005

Tip: Looking for answers? Try searching our database.

vs.net 2005 ide question...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jojobar - 25 Nov 2005 00:26 GMT
okay, I have created an empty project in vs.net 2005 and created a
default.aspx file and a default.aspx.cs file. How can I make the code behind
file (default.aspx.cs) hide so that when I click on show all files icon it
would show up one level below.

This works in web site projects, but I need to make it work on the empty
projects. I think this used to work on vs.net 2003.

Any ideas?

I tried item templates etc. but it did not work. Both aspx file and the
code behind shows up on the same level.

Signature

-jojobar

Mikhail Arkhipov (Microsoft) - 25 Nov 2005 02:54 GMT
On 11/24/05 16:26, in article
67252BCE-B5C6-4EC7-9BB7-1F3199546C71@microsoft.com, "jojobar"

> okay, I have created an empty project in vs.net 2005 and created a
> default.aspx file and a default.aspx.cs file. How can I make the code behind
[quoted text clipped - 8 lines]
>  I tried item templates etc. but it did not work. Both aspx file and the
> code behind shows up on the same level.

In VS 2005 Web projects are very different from client-side projects (In VS
2003 all projects are client) so there is little point in creation of an
empty project and adding aspx file. Create a solution instead and then add a
web site to it.

Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights
jojobar - 25 Nov 2005 15:30 GMT
I understand, but I had a point in asking this. We have a solution that has
about 5000 files divided in 15 different projects. In vs.net 2003, it was not
a problem and all the projects were c# library, and we added aspx, ascx files
into them and vs.net 2003 supported it.

Now while migrating, I find that I am forced to create just one huge
(acutally monstorous!) web project. So I was looking for a workaround.

Are there any? if not, what should I do?!

Other than that vs.net 2005 is great!!!
Signature

-jojobar

> On 11/24/05 16:26, in article
> 67252BCE-B5C6-4EC7-9BB7-1F3199546C71@microsoft.com, "jojobar"
[quoted text clipped - 20 lines]
> Mikhail Arkhipov (Microsoft)
> -- This post is provided 'AS IS' with no warranties and confers no rights
Mikhail Arkhipov (Microsoft) - 26 Nov 2005 08:01 GMT
On 11/25/05 7:30, in article
63FD6E1B-BD2A-463A-837C-EB4E398C3931@microsoft.com, "jojobar"

> I understand, but I had a point in asking this. We have a solution that has
> about 5000 files divided in 15 different projects. In vs.net 2003, it was not
[quoted text clipped - 7 lines]
>
> Other than that vs.net 2005 is great!!!

The best way is probably to create a solution with a single Web site (or as
many Web sites as actually exist on your Web server) and then add Class
Library projects to the solution with output going to bin.

Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.