Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0StarterKit C# ModuleStarterKit C# Module
Previous
 
Next
New Post
7/21/2006 9:10 PM
 
Hi there,

since the starterkit contains a c# module template I wonder what the "regular" way would be to actually use that.
Obviously I cannot add this c# module project to the vb website just by going the "regular" way. So is there a neat trick or do I have to go down the hard way and manually copy everything and make sure that the path infos and references stay intacts.
I kinda get the feeling that there must be an easier way...


Tillman
 
New Post
7/24/2006 7:27 PM
 
Pretty please - anyone?

Can't possibly be that I am the only one who wants to code a DNN 4.x module in C#?
So how would I actually use that C# template in the starterkit?
I would love to get some short hints on what steps to take.

Best regards,

Tillman
 
New Post
7/25/2006 5:53 AM
 

Tillman,

I don't know about the starterkit... but with my BlankModule (you know the one, you've used it :)) it's the same to develop both c# an vb modules because solution implementation rules apply for both project types.

Did you try it with BlankModule?

 


Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

 
New Post
7/25/2006 7:33 PM
 
Actually that's what I just did and the first things went fine but now I am stuck at some strange point.
Apparently I have issues in differentiating between the System.dll and the System.Configuration.dll assembly.
Because VS keeps telling me that:

Error    1    The type or namespace name 'ConfigurationManager' does not exist in the namespace 'System.Configuration' (are you missing an assembly reference?)

Obviouisly I have checked for existence of references to System.Configuration (ASP.NET 2.0 version) and that's obviously not the point. It seems as if the compiler gets confused by the namespace Sytem.Configuration as being a member of the System.dll.


Would you (or anyone) know what to do here?
Of course I could possibly circumvent that issue by using the ASP.NET 1.1 approach but you might imagine that I wanna know what's going on here.


Best regards,

Tillman
 
New Post
7/25/2006 7:41 PM
 
Sometimes you just wish to have the "edit post" option here...

Of course I had added a reference to System.Configuration to my project BUT I did not add that reference to my SqlDataProvider project. Damn...I hate such obvious f*ck ups.

So I will continue my C#-based-on-blank-module endevour...


Cheers,

Tillman
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0StarterKit C# ModuleStarterKit C# Module


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out