|
It's part of the Page class, and this assumes that you are doing this as an ASP.NET page. If you are doing this, then you should really have posted this in the ASP.NET forum.
|
|
|
|
|
Let me be clear enough!I am implementing a web browser in C#.
I need to dynamically change the page currently displayed on a web browser for example I want certain part of the page to be highlighted.
So I am not related to ASP.NET at all.
I think my subject line is the source of misguidance!
Any suggestions for my problem??
|
|
|
|
|
You can always gain access to the Html document through your web browser and then add the javascript to the DOM. This[^] article should give you an idea - but be aware that the webbrowser doesn't expose the IHtmlDocument2 as it stands. In .NET 2, you have to do some work to get the interface.
|
|
|
|
|
I havent been able figure out a way to find the IHTMLDocument interface....
Can u help me out with it???
|
|
|
|
|
From memory - you need to add a reference to MSHTML from Add references... (COM tab). Once you have this referenced in your project you should be able to do this:
IHTMLDocument2 doc = (IHTMLDocument2) webBrowser.Document.DomDocument; As I said, I'm doing this from memory so I apologise if it's MSHTML2 or something like that in the references dialog.
|
|
|
|
|
The method seems to be absolutely fine.....But
How do I add parameters to the javascript which i want to invoke?
Thanks In advance for getting me till here...
|
|
|
|
|
Suppose you have a method called setCanvas that you want to pass a particular div to, you would code this as function setCanvas(div){ /* Do Something */} in the page. Now, to call it dynamically you could use
IHMTLDocument2 doc = (IHTMLDocument2) webBroswer.Document;
if (doc != null)
{
IHTMLWindow2 wind = doc.parentWindow;
string code = "setCanvas('divItem');"
if (wind != null)
wind.execScript(code, "javascript");
}
|
|
|
|
|
string s = File.ReadAllText("s.txt");
mshtml.IHTMLDocument2 doc = (mshtml.IHTMLDocument2)webBrowser1.Document.DomDocument;
if (doc != null)
{
mshtml.IHTMLWindow2 windowx = doc.parentWindow;
if (windowx != null)
{
windowx.execScript(s, "javascript");
}
}
The file s holds a javascript which i want to run plus it takes some arguments to it too....
but it gives me some exception of HRESULT ....can u plz point out the problem
|
|
|
|
|
Aditya Baraya wrote: can u plz point out the problem
Without knowing what the code you were executing actually was, and without knowing the HRESULT then no I can't.
|
|
|
|
|
string s = "alert(hi);";
mshtml.IHTMLDocument2 doc = (mshtml.IHTMLDocument2)webBrowser1.Document.DomDocument;
if (doc != null)
{
mshtml.IHTMLWindow2 windowx = doc.parentWindow;
if (windowx != null)
{
windowx.execScript(s, "javascript");
}
}
The following code is called on a button click event
So I get an exception HRESULT:0x80020101...
Can you plz help me out with this error?
|
|
|
|
|
How do people keep track of build numbers in .net
I've got a project in VS2005 with a deployment project and I'd like to create sequentially numbered releases to keep track of things. This used to be pretty easy in the old VB6 days.
I've found various snippets of code for VS macros that i'm currently trying to get to work but was interested to know what other people do
Does anyone know what the rationale behind non-sequential numbering for versions was?
Russell
|
|
|
|
|
In your AssemblyInfo.cs class, there's a version attribute [assembly: AssemblyVersion("1.0.0.0")]. If you want to increment a part of it automatically on each build, just replace the relevant part with *. So you would end up with [assembly: AssemblyVersion("1.0.0.*")] which automatically increments the * portion on each build.
|
|
|
|
|
Thanks for the reply Pete, I'd tried using that before and it just seems to create a random number, am i missing something?
I'd like to be able to say issue x fixed in version 1.0.0.y and above but the random element makes that impossible.
Thanks,
Russell
|
|
|
|
|
What makes you think its random? Does it ever decrease with a buld?
AFAIK it increments once per build - so separate releases you make will probably have different (but ultimatly increased) number.
|
|
|
|
|
You are correct. Every time you build, the number is incremented.
|
|
|
|
|
That you for confirming that O Sarcastic One.
* bows while stepping backwards *
|
|
|
|
|
J4amieC wrote: That you for confirming that O Sarcastic One.
* bows while stepping backwards *
Sorry - I wasn't actually being sarcastic. I just hoped that the OP would follow the thread and find the confirmation. I would not be sarcastic with a chap of your calibre.
|
|
|
|
|
I was just tugging your chain. The irony was that my response was a thousand times more sarcastic than your response.
|
|
|
|
|
Pete O'Hanlon wrote: the number is incremented
IMO that's both true and misleading.
increment as in "make larger" or "add something positive to it" is correct,
but to a lot of people, myself included, increment means "add one" as is common
in most microprocessor instruction sets.
so maybe the better explanation is AssemblyVersion x.y.z.* or x.y.*.*
generates automatic numbers that contain datetime information in such a way
that the entire number gets increased each time.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Luc Pattyn wrote: IMO that's both true and misleading.
increment as in "make larger" or "add something positive to it" is correct,
but to a lot of people, myself included, increment means "add one" as is common
in most microprocessor instruction sets.
No excuses Luc. I grant you that one.  I should have used increased.
|
|
|
|
|
I was thinking of increment in terms of adding one to something.
It's much harder talking to people and saying the new verion 1.4.5.(between 12764 and 14856) will be available just before lunch than it is to say version 1.4.5.12 will contain the fix for your issue. When I tell people outside the dept that I don't know what version number a fix will be in they look at me like i'm losing my sanity.
Russ
|
|
|
|
|
Hi Russell,
I agree with you on this.
Some companies solve the issue by saying "this feature may be added,
or that bug may be fixed, in a future release of the product" which
is always correct of course.
The way I do it is with 2 or 3 manual parts (hence predictable but
some effort required), the remainder automatic, so each build gives
a different version; and I refer to the manual parts only, not to
the automatic part.
Example: official releases would be 1.1.0.x where x looks random;
and I would call it version 1.1
the next planned release would be 1.2.0.y (or 2.0.0.y), and would
be called either 1.2 or 2.0
And if suddenly a fix is needed, it would be 1.1.1.z (called 1.1.1)
So in the end each release requires an update of AssemblyVersion
to give it a new and callable name.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Thanks,
It seems to be increasing by more than 1 per build but if it's always going to increase then I'll be happy.
CHeers
Russell
|
|
|
|
|
|
Thanks for that, made intersting reading
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
