Welcome Guest! To enable all features please
Login or Register.
Please take a look at this screenshot:
YAF tags not being recognized When I open the source code for yaf in VS 2017 Community Edition, and then open
pages/postmessage.ascx, I am finding that the control tag of YAF and also the method GetPollGroupID() are not being recognized in design view.
I have imported a few namespaces within postmessage.ascx, but it doesn't help.
Question : Is there a trick I am missing in VS 2017 to show the postmessage.ascx without errors?
Edited by user
2018-04-09T06:32:52Z
|
Reason: set issue to solved
Rename the recommend.web.config and add this web.config to the yaf website project, then it should work.
I do not have any web config files and I am using yaf 2.2.3. I have the full source-code of all yaf projects in this solution.
The screenshot of web config files in Solution Explorer is at following url:
Missing Web Config files
I did find the file you mentioned and renamed it web.config file, but still getting the error of YAF tag not being recognized, though GetPollGroupId() method is being recognized now.
I am now getting error in code-behind of postmessage.ascx and also error for one of the controls in postmessage.ascx.
Here are the screenshots:
Errors in Code-behind and
Error in control in design view
I think another problem with postmessage.ascx is that many different types of controls have same tag of
YAFas in markup below.
<%@ Control Language="c#" AutoEventWireup="True" Inherits="YAF.Pages.postmessage" Codebehind="postmessage.ascx.cs" %>
<%@ Import Namespace="YAF.Core" %>
<%@ Import Namespace="YAF.Types.Interfaces" %>
<%@ Import Namespace="YAF.Utils" %>
<%@ Import Namespace="YAF.Types.Extensions" %>
<%@ Import Namespace="YAF.Controls" %>
<%@ Register TagPrefix="YAF" TagName="smileys" Src="../controls/smileys.ascx" %>
<%@ Register TagPrefix="YAF" TagName="LastPosts" Src="../controls/LastPosts.ascx" %>
<%@ Register TagPrefix="YAF" TagName="PostOptions" Src="../controls/PostOptions.ascx" %>
<%@ Register TagPrefix="YAF" TagName="PostAttachments" Src="../controls/PostAttachments.ascx" %>
<%@ Register TagPrefix="YAF" TagName="PollList" Src="../controls/PollList.ascx" %>
<%@ Register TagPrefix="YAF" TagName="AttachmentsUploadDialog" Src="../controls/AttachmentsUploadDialog.ascx" %>
<YAF:PageLinks ID="PageLinks" runat="server" />
<YAF:PollList ID="PollList" ShowButtons="true" PollGroupId='<%# GetPollGroupID() %>' runat="server"/>
At least the yaf solution is now successfully building 15 projects, even though design time errors are there. So that's good enough for me.
Thanks and I appreciate your help on this.
I think its important to close solution and restart VS 2017, in order for web config control changes to take effect.
The errors in design view are normal and will never go away.
The other errors are probably caused because you modified the ascx file before you added the web.config file. This caused the ascx.designer.cs files to regenerate with the wrong controls. Modify that file manually and fix all the yaf controls, or replace the file from the source package.
Why are you using an old version and not the latest version?
The errors in design view are normal and will never go away.
The other errors are probably caused because you modified the ascx file before you added the web.config file. This caused the ascx.designer.cs files to regenerate with the wrong controls. Modify that file manually and fix all the yaf controls, or replace the file from the source package.
Yes, I had made changes to ascx when web config file was not there.
So, you meant to manually modify the ascx.designer.cs files?
Why are you using an old version and not the latest version?
I am using 2.2.3 and have made some changes to source code to better suit my requirements.
Due to these changes, I am hesitant to upgrade since the new version would overwrite all my changes.
Why are you using an old version and not the latest version?
I am using 2.2.3 and have made some changes to source code to better suit my requirements.
Due to these changes, I am hesitant to upgrade since the new version would overwrite all my changes.
Try to create diff patches of the changes you make. Then you can directly apply them after each update
Yes, that is a good suggestion. Right now I am making changes by adding custom user control and including custom JavaScript in separate script file.
But later on, I intend to put these differences into a separate patch.
Yes, that is a good suggestion. Right now I am making changes by adding custom user control and including custom JavaScript in separate script file.
But later on, I intend to put these differences into a separate patch.
Do you know of a good tool for diff patches other than just using TFS for finding differences?
Edited by user
2018-09-18T04:57:33Z
|
Reason: changed my earlier question
What I mean by that is to use git and create a fork with the changes you make. As soon you commit any changes to your forked yaf repository you can create a diff patch from the changes you made. To send a a pull request for example or track the changes you made.
Forum Jump
- You cannot post new topics in this forum.
- You cannot reply to topics in this forum.
- You cannot delete your posts in this forum.
- You cannot edit your posts in this forum.
- You cannot create polls in this forum.
- You cannot vote in polls in this forum.
Important Information:
The YAF.NET Support Forum uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close