So I have been working on an opensource project for a while, and
decided to really try to make it look better after focusing on the
functionality most of this time. Up to now, I have simply used a
standard ASPX page with minor modifications to it. All of my pages
inherit from a "BasePage.c s" class, that handles common things like
getting the user's information out of the session, determines if a page
should or should not be password protected, etc. Up until now it has
all been working fine, but if it ain't broke.. FIX IT right?
Thus I decided to attempt to incorporate MasterPages in my Visual Web
Developer Express since it seemed so easy and would give me much more
control over my pages and allow me to reduce extra ASPX content, etc...
wrong unfortunatly.
Briefly my problems are as follows:
1) I need to get rid of the "ctl001$content Pane$" prefix from my form
collection keynames.
2) I need to elliminate redundant properties that would have to exist
in both my BasePage.cs and MasterPage.cs that access login info, etc
from the session.
More detail follows:
1) The first thing I realized is that when I attempted to login, all of
the keys in the Request.Form NameValueCollec tion had "ctl001$content $"
prepended. I hacked a workaround for this just to see if there were
going to be any other problems, but I would rather NOT have my form
controls prepended with such nonsense, just makes my life more
difficult. I mean, only one server form can exist on a page, why do you
need to specify that it came from a specific content pane, and why is
ctl001 always there if it isn't supposed to change? I mean, this is
going to take another 5 hours to get all working and tested again if I
cannot get rid of this stupid prefix, and it will end up looking VERY
screwey, and I don't want that at all.
2) Again, my BasePage.cs holds userinfo, login status, etc as
properties who's values are actually obtained from the session
underneath. Now it would seem that my MasterPage.cs doesn't have access
to this information, so I would have to put the same properties in the
basepage class in the MasterPage class, so that they can get the info
from the session in a standard way. Then I could have all of the
BasePages actually get the properties from it's masterpage property, or
the code would be redundent otherwise. But this would pose a problem if
there was NO masterpage property of my basepage (IE, a page that didn't
use the masterpage concept). So I am back to having the same property
accessors of the session object repeated in two places. I am really at
a loss for the correct way to fix this. I mean, I am going to have
redundant code in my MasterPage.cs and BasePage.cs file all the ways I
can think of fixing it. I could make some helper class that actually
gets the info from the session that is passed in, but that seems VERY
cludgy, but at least the real guts of the code wouldn't be repeated.
Help help please, I mean, is it supposed to be this difficult to use
MasterPages? Is it realy a situation where you have to use them or not?
What can I do to fix this??
14  2404 
Base page versus master page: Your issue is breaking outside of the
methodology of ASP.NET 2.0, which is forcing dual inheritance. The master
page should eliminate having a separate base class for pages. If you need to
base, for some reason, the master page should inherit from the base to avoid
two paths. I hope this makes sense. I do not have an URL to show what I am
talking about, but it is far simpler than the model you are prescribing.
The $csdklf$asdfjkl as format: Once again, methodology issue. While there are
certainly some rare instances you might have to "hack" at the formatting of
location strings, if you stay within the methodology prescribed, you should
not have to even concern yourself with this. In the rare instances you do,
there are generally methods to provide you with the location specific
formatting you are talking about. This was true in ASP.NET 1.x, as well.
Short Answer: Rather than attempting to recreate something you did elsewhere
in ASP.NET 2.0, take a bit of time experimenting with the model provided and
learn the methology. As it is still beta (well, RC), the documentation is
lagging a bit, but there are plenty of blog entries and websites that explore
master pages to help you out.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** ************
Think Outside the Box!
*************** ************
"mu**********@g mail.com" wrote: So I have been working on an opensource project for a while, and
decided to really try to make it look better after focusing on the
functionality most of this time. Up to now, I have simply used a
standard ASPX page with minor modifications to it. All of my pages
inherit from a "BasePage.c s" class, that handles common things like
getting the user's information out of the session, determines if a page
should or should not be password protected, etc. Up until now it has
all been working fine, but if it ain't broke.. FIX IT right?
Thus I decided to attempt to incorporate MasterPages in my Visual Web
Developer Express since it seemed so easy and would give me much more
control over my pages and allow me to reduce extra ASPX content, etc...
wrong unfortunatly.
Briefly my problems are as follows:
1) I need to get rid of the "ctl001$content Pane$" prefix from my form
collection keynames.
2) I need to elliminate redundant properties that would have to exist
in both my BasePage.cs and MasterPage.cs that access login info, etc
from the session.
More detail follows:
1) The first thing I realized is that when I attempted to login, all of
the keys in the Request.Form NameValueCollec tion had "ctl001$content $"
prepended. I hacked a workaround for this just to see if there were
going to be any other problems, but I would rather NOT have my form
controls prepended with such nonsense, just makes my life more
difficult. I mean, only one server form can exist on a page, why do you
need to specify that it came from a specific content pane, and why is
ctl001 always there if it isn't supposed to change? I mean, this is
going to take another 5 hours to get all working and tested again if I
cannot get rid of this stupid prefix, and it will end up looking VERY
screwey, and I don't want that at all.
2) Again, my BasePage.cs holds userinfo, login status, etc as
properties who's values are actually obtained from the session
underneath. Now it would seem that my MasterPage.cs doesn't have access
to this information, so I would have to put the same properties in the
basepage class in the MasterPage class, so that they can get the info
from the session in a standard way. Then I could have all of the
BasePages actually get the properties from it's masterpage property, or
the code would be redundent otherwise. But this would pose a problem if
there was NO masterpage property of my basepage (IE, a page that didn't
use the masterpage concept). So I am back to having the same property
accessors of the session object repeated in two places. I am really at
a loss for the correct way to fix this. I mean, I am going to have
redundant code in my MasterPage.cs and BasePage.cs file all the ways I
can think of fixing it. I could make some helper class that actually
gets the info from the session that is passed in, but that seems VERY
cludgy, but at least the real guts of the code wouldn't be repeated.
Help help please, I mean, is it supposed to be this difficult to use
MasterPages? Is it realy a situation where you have to use them or not?
What can I do to fix this??
Ok, not trying to argue, I appreciate your prompt answer, but I have a
few questions about what you suggested, also, here is a link that
explains the complexity of the project: http://www.codeproject.com/aspnet/RapidWebAppDev.asp
1. Ok, I guess I can use a masterpage class to hold my stuff for every
page. But what happens if I don't want to use the masterpage, but still
want the functionality that a BasePage provides (IE a Login protected
Popup window). Also, the master page cannot inherit from the base as
you suggested because the BasePage inherits from a Page, not from a
MasterPage, thus turning my MasterPage.cs into a regular Page. Am I
missing something?
** Action ** I am going to move forward with this suggestion, but I
still want to know how Microsoft expects us to have both a Regular Page
and MasterPage that inherit some common functionality? Seems that they
should have made EVERY page "MasterPage " capable, but they split the
two out for some reason. Fortunatly in my situation, there would not be
a lot of code that would be duplicated, but that may not be true
elsewhere, and I want to avoid that if at all possible.
2. I cannot think of a reason to qualify the input names in such a way,
all controls must have a unique ID, so there would be no ambigious
references. Having to prepend mu collection key with the SAME thing
over and over again seems redundant. Also, the code will break if the
pane changes names (IE code re-used in another project). This is going
to require lots of work for people to modify their existing ASP.Net
code. Do you have any insight as to what the advantage of this is?
Everyone I have talked to about this agrees with me, qualifying input
names in such a manner simply isn't needed. The only thing I can think
of is that you could have the same control ID in different content pane
pages, but you should get a parser error from the server in that case.
** Action ** I am currently just thinking to make a new namevalue
collection (since Request.From is readonly) and key it's values with
everything to the right of the last $ sign, and replacing all
"request.fo rm" with "OriginalFo rm" or something similar. And while it
would be a relativly simple fix, this is something that shouldn't have
been broken in the first place IMHO.
Again, not trying to argue, trying to understand :D
AB
On 10 Oct 2005 08:37:38 -0700, mu**********@gm ail.com wrote:
Help help please, I mean, is it supposed to be this difficult to use
MasterPages? Is it realy a situation where you have to use them or not?
What can I do to fix this??
I have great reservations about putting common functionality into a
master page, I wrote about the topic here:
Master Page Anti-pattern http://odetocode.com/Blogs/scott/arc...9/10/2179.aspx
I'd stick with a base page for my web forms. If this base page class
lives in App_Code you can always cast the Page property of the master
to that type and interact with the page in a stronly typed manner.
Am I making sense?
--
Scott http://www.OdeToCode.com/blogs/scott/
Oops! I was the one off track on this one (brain death?). I have been jumping
from 2.0 to DotNetNuke to a custom portal a friend wrote that I messed up on
which used an inherited master page and which implemented a master page as a
control. A quick look at the 2.0 bits showed my stupidity. I apologize for
jumping without checking myself.
Please note, I have not played around with the code you reference
completely, so I am still being a bit generic here.
1. You can inherit from your base page and put functionality into the base
page. Be careful which elements you place here and which are best placed in
the master page. The main thing the master page does for you is make it so
you can avoid repeating elements in multiple pages. If you are handling this
through inheritance, the master page may be unnecessary. In other words,
master pages help you more when you are using the designer than when you are
coding your own elements.
2. The master page is a control when rendered (kind of strange, perhaps, but
the UI handles it for you (this is my brain death element, of course)). To
get events from the master to the page, you can bubble up through delegates
(events in VB.NET). Just have your basepage class handle the delegate or
implement in pages where it should be handled and ignore in others (do not
prefer the later, however, as a good design should not have clicks to
nowhere). This can help with some of your common elements. As it renders as a
control on the page, grabbing the content areas when compiled, your page can
still handle the calls. Hope this makes sense.
3. To avoid naming issues, set up your controls (master page, user controls,
etc.) as black boxes. This means that you have to access the members via
methods and properties. This gives you a couple of options:
a) page as handler: The page grabs from the various controls and submits any
information in one pass. You can use a strongly typed dataset to handle data
access and populate the different tables from different controls. Make the
ToString() method return your dataTable as XML, for example.
b) control as handler: Each control is responsible for its own data. This
makes the app a bit chattier, but encapsulates the code better. If you head
this route, you should set up, at mimimum, an interface that checks validity
of the data in each control (IsValid() method, for example) and only call the
save method on the user control when all controls on the page that implement
the interface give a true for IsValid(). You can reduce chatter, a bit, by
having the page connect and pass the connection to each control, but this can
be troublesome, as well. The benefit of this method is user controls can map
directly to user objects, which can inherit from strongly typed DataSets.
Nice, easy model.
I will have to look at the popup login to get a better idea of what you are
aiming at. The code sample you reference does not appear to have the master
page ( http://www.codeproject.com/aspnet/RapidWebAppDev.asp), so I am not sure
if that is the full 2.0 implementation you are talking about or not.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** ************
Think Outside the Box!
*************** ************
"mu**********@g mail.com" wrote: Ok, not trying to argue, I appreciate your prompt answer, but I have a
few questions about what you suggested, also, here is a link that
explains the complexity of the project:
http://www.codeproject.com/aspnet/RapidWebAppDev.asp
1. Ok, I guess I can use a masterpage class to hold my stuff for every
page. But what happens if I don't want to use the masterpage, but still
want the functionality that a BasePage provides (IE a Login protected
Popup window). Also, the master page cannot inherit from the base as
you suggested because the BasePage inherits from a Page, not from a
MasterPage, thus turning my MasterPage.cs into a regular Page. Am I
missing something?
** Action ** I am going to move forward with this suggestion, but I
still want to know how Microsoft expects us to have both a Regular Page
and MasterPage that inherit some common functionality? Seems that they
should have made EVERY page "MasterPage " capable, but they split the
two out for some reason. Fortunatly in my situation, there would not be
a lot of code that would be duplicated, but that may not be true
elsewhere, and I want to avoid that if at all possible.
2. I cannot think of a reason to qualify the input names in such a way,
all controls must have a unique ID, so there would be no ambigious
references. Having to prepend mu collection key with the SAME thing
over and over again seems redundant. Also, the code will break if the
pane changes names (IE code re-used in another project). This is going
to require lots of work for people to modify their existing ASP.Net
code. Do you have any insight as to what the advantage of this is?
Everyone I have talked to about this agrees with me, qualifying input
names in such a manner simply isn't needed. The only thing I can think
of is that you could have the same control ID in different content pane
pages, but you should get a parser error from the server in that case.
** Action ** I am currently just thinking to make a new namevalue
collection (since Request.From is readonly) and key it's values with
everything to the right of the last $ sign, and replacing all
"request.fo rm" with "OriginalFo rm" or something similar. And while it
would be a relativly simple fix, this is something that shouldn't have
been broken in the first place IMHO.
Again, not trying to argue, trying to understand :D
AB
It certainly does require the study of the scant tutorials and documentation
that are available and it seems to me the use of a base class is a common
sense requirement as the Master Page is said to be a compiled as if it were
a user control and does not support the new Page_PreInit event which is the
only event which supports programatically changing the master or themes.
Given no use of a base class each page that inherits from System.Web.UI.P age
would require redundant code throughout the entire application.
The Cowboy has the experience but I'm confused about his claim regarding two
paths of inheritence. Noting I have little experience using base class
inheritence and shorten the declaration for brevity about three weeks ago I
tried the following...
.... MyMaster : System.Web.UI.M asterPage, System.Web.UI.P age
and...
.... MyMaster : System.Web.UI.M asterPage, MyBaseClass
neither of which would compile.
So I've adopted the use of a base class as I require its support for the
Page_PreInit event to change masters and themes programmaticall y.
I've also been compelled to use a base class to maintain control state of
styles applied to tabbed navigation I created using LinkButtons. I'm sure
there's so much more value using base classes and I'm sure there's likely
other strategies to achieve the same objectives but the need to use the
Page_PreInit event puts the entire arguement to rest as there's no way I
want to develop and maintain what may be dozens of pages with redundant
events that only need to be raised and managed once in a base class. That's
how I understand it at this point in time.
search: page_preinit
search: page_preinit site:msdn2.micr osoft.com
As for other Master Page issues, besides others, you also need to do this
search...
search: MasterType site:msdn2.micr osoft.com
I've learned referencing controls is done two ways: FindControl method (late
bound0 and Properties (early bound). I've been using both and now work on
learning how to choose when and where using either is most beneficial. The
FindControl method is tricky to learn to use with Master Pages when a
control is contained within another control. Trying to find a LinkButton
within a Panel in a Master Page comes to mind.
As for the naming of the control tree items each apparently remains
addressable in the client or from the server but doing so is brittle as any
change to the page reorders and renames items in the control tree.As I
recall, disabling the Visible property of a control for example will remove
the control from the tree and ruffle new values through that section of the
tree. Very challenging for an intermediate like myself to really master.
<%= Clinton Gallagher
<mu**********@g mail.com> wrote in message
news:11******** **************@ g49g2000cwa.goo glegroups.com.. . Ok, not trying to argue, I appreciate your prompt answer, but I have a
few questions about what you suggested, also, here is a link that
explains the complexity of the project:
http://www.codeproject.com/aspnet/RapidWebAppDev.asp
1. Ok, I guess I can use a masterpage class to hold my stuff for every
page. But what happens if I don't want to use the masterpage, but still
want the functionality that a BasePage provides (IE a Login protected
Popup window). Also, the master page cannot inherit from the base as
you suggested because the BasePage inherits from a Page, not from a
MasterPage, thus turning my MasterPage.cs into a regular Page. Am I
missing something?
** Action ** I am going to move forward with this suggestion, but I
still want to know how Microsoft expects us to have both a Regular Page
and MasterPage that inherit some common functionality? Seems that they
should have made EVERY page "MasterPage " capable, but they split the
two out for some reason. Fortunatly in my situation, there would not be
a lot of code that would be duplicated, but that may not be true
elsewhere, and I want to avoid that if at all possible.
2. I cannot think of a reason to qualify the input names in such a way,
all controls must have a unique ID, so there would be no ambigious
references. Having to prepend mu collection key with the SAME thing
over and over again seems redundant. Also, the code will break if the
pane changes names (IE code re-used in another project). This is going
to require lots of work for people to modify their existing ASP.Net
code. Do you have any insight as to what the advantage of this is?
Everyone I have talked to about this agrees with me, qualifying input
names in such a manner simply isn't needed. The only thing I can think
of is that you could have the same control ID in different content pane
pages, but you should get a parser error from the server in that case.
** Action ** I am currently just thinking to make a new namevalue
collection (since Request.From is readonly) and key it's values with
everything to the right of the last $ sign, and replacing all
"request.fo rm" with "OriginalFo rm" or something similar. And while it
would be a relativly simple fix, this is something that shouldn't have
been broken in the first place IMHO.
Again, not trying to argue, trying to understand :D
AB
Your tutorials have been making sense for me Scott. Thank you for being one
of the few guys who has taken the time to do this work although there's been
a time or two I wanted to put both hands around your scrawny little neck and
squeeze until your eyes popped out :-) (I think I've watched too much TV).
Some of the tutorials lead to a critical point in understanding the context
of the topic and then poop out and stop right then and there. No, I'm, sorry
I don't remember which one(s).
<%= Clinton Gallagher
"Scott Allen" <sc***@nospam.o detocode.com> wrote in message
news:ia******** *************** *********@4ax.c om... On 10 Oct 2005 08:37:38 -0700, mu**********@gm ail.com wrote:
Help help please, I mean, is it supposed to be this difficult to use
MasterPages ? Is it realy a situation where you have to use them or not?
What can I do to fix this??
I have great reservations about putting common functionality into a
master page, I wrote about the topic here:
Master Page Anti-pattern
http://odetocode.com/Blogs/scott/arc...9/10/2179.aspx
I'd stick with a base page for my web forms. If this base page class
lives in App_Code you can always cast the Page property of the master
to that type and interact with the page in a stronly typed manner.
Am I making sense?
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Mon, 10 Oct 2005 14:14:10 -0500, "clintonG"
<cs*********@RE MOVETHISTEXTmet romilwaukee.com > wrote: Your tutorials have been making sense for me Scott. Thank you for being one
of the few guys who has taken the time to do this work although there's been
a time or two I wanted to put both hands around your scrawny little neck and
squeeze until your eyes popped out :-) (I think I've watched too much TV).
Some of the tutorials lead to a critical point in understanding the context
of the topic and then poop out and stop right then and there. No, I'm, sorry
I don't remember which one(s).
Thanks for the compliment, Clinton. At least I think it was a
compliment :)
--
Scott http://www.OdeToCode.com/blogs/scott/
It was a bit backhanded, but it sure sounded like a complement. :-)
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** ************
Think Outside the Box!
*************** ************
"Scott Allen" wrote: On Mon, 10 Oct 2005 14:14:10 -0500, "clintonG"
<cs*********@RE MOVETHISTEXTmet romilwaukee.com > wrote:
Your tutorials have been making sense for me Scott. Thank you for being one
of the few guys who has taken the time to do this work although there's been
a time or two I wanted to put both hands around your scrawny little neck and
squeeze until your eyes popped out :-) (I think I've watched too much TV).
Some of the tutorials lead to a critical point in understanding the context
of the topic and then poop out and stop right then and there. No, I'm, sorry
I don't remember which one(s).
Thanks for the compliment, Clinton. At least I think it was a
compliment :)
--
Scott
http://www.OdeToCode.com/blogs/scott/
Yes, it was.
<%= Clinton Gallagher
"Cowboy (Gregory A. Beamer) - MVP" <No************ @comcast.netNoS pamM> wrote
in message news:0E******** *************** ***********@mic rosoft.com... It was a bit backhanded, but it sure sounded like a complement. :-)
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** ************
Think Outside the Box!
*************** ************
"Scott Allen" wrote:
On Mon, 10 Oct 2005 14:14:10 -0500, "clintonG"
<cs*********@RE MOVETHISTEXTmet romilwaukee.com > wrote:
>Your tutorials have been making sense for me Scott. Thank you for being
>one
>of the few guys who has taken the time to do this work although there's
>been
>a time or two I wanted to put both hands around your scrawny little neck
>and
>squeeze until your eyes popped out :-) (I think I've watched too much
>TV).
>Some of the tutorials lead to a critical point in understanding the
>context
>of the topic and then poop out and stop right then and there. No, I'm,
>sorry
>I don't remember which one(s).
>
Thanks for the compliment, Clinton. At least I think it was a
compliment :)
--
Scott
http://www.OdeToCode.com/blogs/scott/ This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics | |
by: Murphy |
last post by:
I have read the articles by Paul Wilson regarding master pages, and apart
from being totally confused I would like to clarify the following before
investing any further time on researching these concepts.
Are master pages reliable or are they a buggy concept ?
I understand master pages will be included in the next version of the
framework ?
Is there a reason not to use them presently ?
Where can I obtain further documentation of the...
|
by: Nils Magnus Englund |
last post by:
Hi!
I'm playing around with Wilson's master pages for ASP.NET 1.1. It seems ok,
but I'm really struggling with the following two problems:
1)
I want all .aspx pages to inherit from the same codebehind (lots of static
content). Some pages have a different menu. I want to be able to, in the
individual .aspx pages, be able to add e.g. <mp:content id="menu"
|
by: Michael Herman \(Parallelspace\) |
last post by:
1. What are some compelling solutions for using Master/Content pages with
Web Pages?
2. If a content area has a web part zone with web parts, what is the user
experience like when "editting" the web part page? Does it take place at
the page level? ...or the content area level?
3. Where is the Web Part Manager instantiated? ...in the Master Page?
....Content Page? ...elsewhere?
|
by: M.Siler |
last post by:
Let me first by saying I am NOT a .net programmer, but am very skilled with
ASP, JavaScript, HTML, DHTML, Flash development.
I've been reading through posts here about Frames vs. Master Pages and there
seems to be the thought of why use Frames when you can use a Master Page?
How does a Master Page only update a section without re-displaying the
entire page. We have a site that has some small swf banners for lack of a
better term that we...
|
by: EagleRed |
last post by:
I am writing an ASP.NET 2.0 application that uses more than one master page.
Currently, there are two pages, Freedom1.master and Freedom2.master. I have
no problems with Freedom1.master. However, I am having problems with
Freedom2.master.
The first problem is I sometimes get the following error when I build the
site.
The type 'Freedom2' exists in both
'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
| | |
by: Andy |
last post by:
Hey all,
I'm building out my first project using asp.net v2.0 master pages. It seems
that when you use master pages and try to reference document.body.scrollTop
it allways = zero/0. The same code works in a regular .htm file.
Has anyone else seen this?
Anyone know how to get the body.scrollTop property using masterpages.
Thanks for any help
Andy
|
by: D |
last post by:
Hi,
I've been toying around with master pages and am trying to set up your
standard banner across the top and 3 areas below that, left content, center
content and right content.
I have the banner part being the top level master page and the left content
be nested master page named subMaster.master. In this I have 3 div's that
I've named
|
by: Greg Collins [Microsoft MVP] |
last post by:
I have a situation where a particular error page is being redirected to (Server.Transfer) and in most cases it works correctly loading the correct master page and rendering as it should.
In another case, this page is being called as a result of an asp:Xml failure, but the Server.Transfer seems to maintain the existing hierarchy of master pages, and thus the page is framed twice when rendered. (Response.Redirect actually works correctly here...
|
by: TheLongshot |
last post by:
I just recently converted a few pages of my application to using master
pages. Problem is, in all of my content pages, the contents are
centered. I can't figure out why. The markup in the content page
seems to ignore any attempts to manually align right. So what's the
deal?
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
| | |
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| | |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| | |
