ASP.NET

how to remove dll reference in visual studio?

16-Jan-09 12:21

You should really avoid the use of Server.Transfor for such simple scenarios like this. ASP.NET allows you to cross-post from one page to another. Just set the PostbackURL property on the button to page2.aspx, and access the value for txtFirstPage directly from the form: Request.Form["txtFirstPage"]

mr_muskurahat16-Jan-09 0:44

mr_muskurahat

16-Jan-09 0:44

can any one guide me how can i do it i have added a dll reference in toolbox and now i want to remove it complete from my visual studio.

any suggesion would be appriciated..

umerumerumer

Re: how to remove dll reference in visual studio?

Abhijit Jana16-Jan-09 20:55

Abhijit Jana

16-Jan-09 20:55

mr_muskurahat wrote:
i want to remove it complete from my visual studio.

Right Click on toolbox and Click Reset Tool Box
Or
Right Click on Toolbox > Choose ToolBox Item > Unchecked the components that you have add > Ok

BTW : Does it any thing related with ASP.Net Smile | :)

cheers,
Abhijit
CodeProject MVP
My Recent Article : Exploring Session in ASP.Net

merge two pdf

bhaumikdv16-Jan-09 0:11

bhaumikdv

16-Jan-09 0:11

i want to merge two pdf files... the thing is that the content of tha file should not be lost ... i just want to append the data in file..

Re: merge two pdf

SeMartens16-Jan-09 3:45

SeMartens

16-Jan-09 3:45

Hi,

there are a lot of tools out there that can merge pdfs. For example PDF Split and Merge (http://www.pdfsam.org/[^]). This app can be controled by console. So all you have to do is to start a process within your app using this tool by console.

Does this help you?

Regards
Sebastian

It's not a bug, it's a feature!

Check out my CodeProject article Permission-by-aspect.

Me in Softwareland.

[Message Deleted]

mihirkul15-Jan-09 23:33

mihirkul

15-Jan-09 23:33

[Message Deleted]

CP IGNORE; repost

leckey16-Jan-09 4:21

leckey

16-Jan-09 4:21

You need to learn how to put your code in the proper tags.

"Well, we're getting "F"'d at work. WPF, WCF, and WWF... WTF?" --John Simmons

Datagrid with row movement by mouse clicking

Girish48115-Jan-09 23:12

Girish481

15-Jan-09 23:12

Hello,

I am trying to implement the code provided at this link:
http://www.danielsoper.com/programming/DataGridViewDragDropRowsColumns.aspx

I have populated the datagrid from oracle table; but it is returning error when i close/end the application. "No symbols are loaded for any call stack frame. The source code cannot be displayed" and then another message box appears which title is "LoaderLock was detected".

Please try at your end and let me know to correct the error.

Regards
Girish

Re: Datagrid with row movement by mouse clicking

Ashfield16-Jan-09 1:28

Ashfield

16-Jan-09 1:28

Have you tried running in debug? Have you tried asking the code author? Those should be your first steps.

Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP

Checkbox in datagrid!

RajpootRohan15-Jan-09 22:37

RajpootRohan

15-Jan-09 22:37

Hi to all,

I have a datagrid and a checkbox in it.In my datagrid I have a template column of "QTY" which is having a textbox.
Suppose user selects an item then it will be displayed in the datagrid.

But if user wants to change the quantity then he has to check the the checkbox and click the update button below datagrid.

for this I did:

<br />
<asp:DataGrid ID="DataGrid2" runat="server" CellPadding="4" ForeColor="#333333" <br />
            GridLines="Horizontal" EnableViewState="False" Font-Bold="True" <br />
            Font-Names="Verdana" Font-Size="Small" AutoGenerateColumns="False" ><br />
            <FooterStyle BackColor="#5D7B9D" Font-Bold="True" ForeColor="White" /><br />
            <EditItemStyle BackColor="#999999" /><br />
            <SelectedItemStyle BackColor="#E2DED6" Font-Bold="True" ForeColor="#333333" /><br />
            <PagerStyle BackColor="#284775" ForeColor="White" HorizontalAlign="Center" /><br />
            <AlternatingItemStyle BackColor="White" ForeColor="#284775" /><br />
            <ItemStyle BackColor="#F7F6F3" ForeColor="#333333" /><br />
            <Columns><br />
            <asp:TemplateColumn HeaderText="Select" HeaderStyle-Width="50px"><br />
            <ItemTemplate><br />
            <asp:CheckBox ID="chkSelection" runat="server" ToolTip='<%# Eval("QTY") %>' /><br />
            </ItemTemplate><br />
            <HeaderStyle Width="50px"></HeaderStyle><br />
            </asp:TemplateColumn><br />
                <asp:BoundColumn DataField="REF" HeaderStyle-Width="70px" HeaderText="REF"></asp:BoundColumn><br />
                <asp:TemplateColumn HeaderText="product_id" Visible="False"><br />
                <ItemTemplate><br />
                <asp:Label ID="lblProduct_Id" runat="server" Text='<%# Eval("REF") %>'></asp:Label><br />
                </ItemTemplate><br />
                </asp:TemplateColumn><br />
                <asp:BoundColumn DataField="Description" HeaderStyle-Width="330px" HeaderText="Description"></asp:BoundColumn><br />
                <asp:TemplateColumn HeaderText="QTY" HeaderStyle-Width="30px"><br />
                <ItemTemplate><br />
                <asp:TextBox ID="TxtQTY" runat="server" Width="30px" Text='<%# Eval("QTY") %>' /><br />
                </ItemTemplate>               <br />
                </asp:TemplateColumn><br />
                <asp:BoundColumn DataField="Price" HeaderStyle-Width="50px" HeaderText="Price"></asp:BoundColumn><br />
                <asp:BoundColumn DataField="Cost" HeaderStyle-Width="70px" HeaderText="Cost"></asp:BoundColumn><br />
            </Columns><br />
            <HeaderStyle BackColor="#5D7B9D" Font-Bold="True" ForeColor="White" /><br />
        </asp:DataGrid><br />

protected void BtnUpdate_Click(object sender, EventArgs e)
{
    CheckBox chkSelected = new CheckBox();

    foreach (DataGridItem dgItem in DataGrid2.Items)
    {
        chkSelected = (CheckBox)dgItem.FindControl("chkSelection");

        if (chkSelected.Checked == true)
        {
            qty3 = Convert.ToInt32(chkSelected.ToolTip);
        }

    }
}

But the problem is that in the code behind file datagrid2.Items has the count=0.So the foreach loop is not working.

Please guide me that where I am making mistake.
Thanks in advance!

cheers,
sneha

Re: Checkbox in datagrid!

Christian Graus15-Jan-09 23:26

Christian Graus

15-Jan-09 23:26

I'd suggest that you need to look at where your databinding occurs and if viewstate is turned on. If you databind in your page load every time, that runs first and causes viewstate to be lost.

Christian Graus

Driven to the arms of OSX by Vista.

Re: Checkbox in datagrid!

Herman<T>.Instance19-Jan-09 3:34

Herman<T>.Instance

19-Jan-09 3:34

your foreach statement should be put in the GridView OnRowDataBound-method.
In the btnUpdate_click you should determine in whicht line the click was made. With that information you could do an sqlquery and then bind that data to the gridview. The OnRowDataBound -method is then fired after each placed row in the griview.

How to get a particular sub report of any report programaticaly ?

bhaumikdv15-Jan-09 22:20

bhaumikdv

15-Jan-09 22:20

I have one report which consist subreport also. now i just want to display subreport of that report... so if any 1 of u knw pls reply me..

MVP implementation questions

Nathan Gloyn15-Jan-09 21:59

15-Jan-09 21:59

I'm currently looking into using the MVP pattern for creating web applications and have some questions:

- If state needs to be recorded I presume its done in the model, if the model classes are in an assembly separate from the actual pages do you still use session or some other form of state management?

- How is UI logic such as "disable this button unless condition is met" handled? is the logic embedded in the view ( or the page code behind), presenter or model.

Can any body can provide some detail/thoughts in relation to these areas?

N a v a n e e t h15-Jan-09 23:04

N a v a n e e t h

15-Jan-09 23:04

Lowest of the Low wrote:
MVP pattern for creating web applications

IMO, MVP is most suitable for stand-alone applications and MVC is more suitable for web applications.

Lowest of the Low wrote:
If state needs to be recorded I presume its done in the model, if the model classes are in an assembly separate from the actual pages do you still use session or some other form of state management?

If the model is in separate assembly and to use session, you need a reference to System.Web assembly and hence making it strongly coupled. To avoid this, you can wrap the state management in well defined interfaces and inject to the model using dependency injection. So that your model will be isolated.

Lowest of the Low wrote:
How is UI logic such as "disable this button unless condition is met" handled? is the logic embedded in the view ( or the page code behind), presenter or model.

Passive View approach will be obvious for this.

Here are few links which will help

1 - Passive view - A .NET approach[^]
2 - MVP in ASP.NET[^]

Hope this helps Smile | :)

Navaneeth

How to use google | Ask smart questions

Nathan Gloyn16-Jan-09 4:00

16-Jan-09 4:00

Thanks for the response.

MVC is not currently an option for us (new technology...risk...etc, etc) but changing our existing webforms development to use MVP is something that could be done.

I looked at Phil Haack's ASP.NET Supervising Controller (Model View Presenter) From Schematic To Unit Tests to Code[^] which looks good.

I still have other questions like where is validation done? And in relation to your comment on injecting state via interface I'm being a bit thick today but how? Surely if I use session I'd still need a reference to System.Web? or are you suggesting that I could provide access to session through another object?

N a v a n e e t h16-Jan-09 5:05

N a v a n e e t h

16-Jan-09 5:05

Lowest of the Low wrote:
MVC is not currently an option for us (new technology...risk...etc, etc)

Well, I was not talking about the ASP.NET MVC framework. I was talking about the MVC concept.

Lowest of the Low wrote:
I still have other questions like where is validation done?

For trivial validations, view is the appropriate place. But if you have very complex business validations, you probably need put it outside of the view.

Lowest of the Low wrote:
And in relation to your comment on injecting state via interface I'm being a bit thick today but how?

You define an interface with the necessary properties and methods. Implement this interface in the same project where you have access to session. Then inject this interface instance to model(or whatever area). Read about dependency injection[^].

Navaneeth

How to use google | Ask smart questions

Nathan Gloyn16-Jan-09 5:38

16-Jan-09 5:38

Query for you on the Dependency injection, does that not violate the OOP "Dependency Inversion Principle"?

Jon Rista16-Jan-09 5:59

16-Jan-09 5:59

The general goal behind MVP is to isolate as much logic from the "view" as possible, just like with MVC. The benefits of MVP over MVC are primarily realized when a complete rewrite of an existing WebForms app into an MVC framework can't be done (which sounds like your situation).

I've implemented MVP a couple times for existing ASP.NET WebForms sites, and its been quite successful. In terms of managing state, etc. There are a lot of different kinds of state, and it depends on what state your talking about. ASP.NET WebForms state should probably be keept in the same locations it would have been keept before for basic stuff. If you had a ViewState property on a Page that held a CustomerID, for example, you should probably keep it in the Page ViewState.

As for logic...put as much as humanly possible in the Presenter. The presenter is like the controller from MVC, and one of the main reasons for having it is to allow you to maintain SoC, separation of concerns. A view is just a representation of data, and it really shouldn't contain logic. In the case of WebForms, it will probably need to contain a little bit to handler data set on it by the presenter and render it, but keep it minimal. The presenter should handle all the logic of processing your page, it should contain event handlers to handle events on the view (including events inherited from Page and Control), it should validate input, and decide when to enable/disable controls.

The view should be a standard WebForms .aspx page with codebehind. However, in addition, you will need to create and implement an interface that represents your view. This interface is the access point for the presenter. The proper form of either Passive View or Supervising Controller MVP is that the presenter does not maintain any direct references to the view, only to an interface that represents the view. This allows the presenter to be used for multiple similar views. The view itself should handle the process of creating the presenter, and passing itself to the presenter (thats how the presenter gets a reference to the views interface). This view interface should contain all properties and events on the view, as well as exposing common stuff from the Page class as well, such as the standard page events (OnInit, OnLoad, OnPreRender, etc.)

If you need any more help, I'd be glad to offer it. I have a small MVP framework that I've written that is very lightweight and easy to integrate into existing apps a view at a time, with little configuration. I have considered writing an article about it for a while, maybe the time is right. Most people don't fully realize the benefit of MVP for ASP.NET when you don't have the option of rewriting the whole site as an MVC app (using any MVC framework). MVP is a great way to improve SoC and increase unit testability without requiring a massive rewrite of an existing application.

Nathan Gloyn16-Jan-09 8:50

16-Jan-09 8:50

You've hit my situation on the head, said I was being a bit thick earlier today couldn't even explain the situation I'm in very well.

In work we have moved to an agile way of working involving a lot of TDD and that is one of the main drivers for looking to try and move to a MVP style of development.

The state issue is a concern because we do use session for storing some info and currently we have to reference System.Web in our existing equivilant of the model and this is one of the main issues I need to try and overcome before being able to implement MVP.

Any thoughts you've got would be appreciated.

Jon Rista16-Jan-09 9:21

16-Jan-09 9:21

I would be glad to help. There is a lot of rave these days about MVC, partially because of greater TDD movements, partly because of ASP.NET MVC. MVC is definitely nice, but its not the solution to every presentation problem.

I would like to get a bit more information about your exact scenario. From a rigid design perspective, your Model should be abstracted away from the views as much as possible, completely isolated even. The "bridge" between view and model is the presenter/controller. It depends on the scale of the application, but model could actually be a full Domain Model. Its also possible that you have a domain, but it is isolated by a set of services. Sometimes people share their domain accross the wire from services, but going back to the core principals of programming...Separation of Concerns, Single Responsibility, Isolation, etc. it might be best to have a presentation-specific model that you create from your domain or whatever your services return to give you an added degree of separation and testability.

Anyway...if you can give me a concrete example (you can keep it simple) of how your view, presenter, and model are interacting now (or would), and note where your storing state or having state issues, I'll see what I can do to help you organize it better. Sometimes its just a matter of the wrong class doing something useful...and splitting the class in two and putting the other part in a different namespace/project solves the problem.

Nathan Gloyn16-Jan-09 9:41

16-Jan-09 9:41

ok here's the details:

The current application effecively has View and model but no presenter but the app does generally follow good OOP with SoC, Single Responsibility, Create don't use etc.

All business logic and db access is handled in the model which is in a seperate assembly and has been created as a domain model.

A fair amount of model information is accessed through properties which store their data in session (the model is closer to a desktop type app than a web app).

The code behind's of the pages mostly data bind to the properties exposed by the model although there is a lot of logic around controlling the UI (including a hack of the treeview to add a link to child nodes). Whilst ViewState is not disabled it is generally not used for storing of any particular stateful information.

One reason for the need to store the stateful information is that the application is generally driven by meta data so that when different clients access the application the app points to a different database and calls different stored procedures when working the data.

We use code from Phil Haack for simulating HttpSession to allow us to perform unit tests on the model, and we have fairly good coverage over the classes.

The application works well enough but it seems a good candidate for refactoring as its fairly simple but meaty enough to present a challenge.

Jon Rista16-Jan-09 10:02